Migrate from Ziggu to Pipedrive

Ziggu contacts who are clients or homebuyers map directly to Pipedrive Persons. Name, email, phone, and address fields transfer 1:1. Ziggu's contact record may reference a Company — that parent link becomes an Organization lookup in Pipedrive via the person_id/org_id relationship.

Ziggu company records (builders, contractors, partner firms) map to Pipedrive Organizations. Company name, domain, industry, and employee count transfer as Organization fields. Address, phone, and any custom properties also migrate via POST /organizationFields. Ziggu's parent-company hierarchy (if used) maps to the Organization's parent_org_id field in Pipedrive.

A Ziggu Unit (an individual property unit within a development project) maps to a Pipedrive Deal. The Unit name becomes the Deal title, the agreed sale price becomes the Deal value, and the Unit's status (Reserved, Sold, Completed) maps to a Pipeline Stage in Pipedrive. Multiple Units in one Project can share a parent Deal or map individually based on your pipeline definition.

Ziggu Projects have no direct Pipedrive equivalent. We create a Project__c custom field on the Deal object and store the project name, project code, and development type (residential, commercial, mixed-use) as fields. Alternatively, a parent Deal representing the project can own child Deals representing Units — your admin chooses the structure before migration runs.

Ziggu Conversation threads linked to a specific Unit or Contact are converted to Pipedrive Notes (for written client exchanges) or Activity records (for action-oriented tasks that emerged from a conversation). The original thread URL is stored in a custom field so the conversation remains accessible if needed.

Ziggu Tasks assigned to team members or clients map to Pipedrive Activities with type='task'. The task title, due date, and assigned owner transfer. Pipedrive Activity owners are resolved by email match against Pipedrive users. Completed status maps to the done field (1=completed, 0=open).

Ziggu Documents (floor plans, specifications, contracts) linked to Units or Contacts are downloaded and re-uploaded to Pipedrive Files attached to the corresponding Deal or Person. Pipedrive's file size limit is 100MB per file. We preserve the original document name and a link back to the Ziggu source if the Ziggu account remains accessible.

Ziggu Survey responses attached to a Contact or Unit have no Pipedrive native equivalent. We create custom fields on the Person (for NPS or preference surveys) or Deal (for unit-selection surveys) and store the response value, response date, and survey name. Survey logic and distribution rules must be rebuilt in Pipedrive's workflow automation or a dedicated survey tool post-migration.

Ziggu Approvals (client sign-offs on selections, contracts, or milestones) are captured as a custom Approval_Status__c field on the corresponding Deal, plus an Activity with type='task' noting the approval date and approver. The approval chain and deadline logic from Ziggu must be rebuilt in Pipedrive's Automations.

Ziggu allows custom properties on Units (e.g., floor_level, unit_type, facing_direction, completion_percentage). We create matching Pipedrive Deal custom fields via POST /dealFields before data migration begins. Field type mapping is done by Ziggu's property type: text to varchar, number to int, date to date, pick-list to enum.

Ziggu contacts may carry custom properties beyond standard fields (e.g., preferred_contact_method, referral_source). We create matching Pipedrive Person custom fields via POST /personFields before migration. Email and phone custom fields follow standard field creation; multi-select values are stored as comma-separated strings or as enum fields if Pipedrive's field type supports it.

Ziggu Partner Portal companies (suppliers, contractors) map to Pipedrive Organizations. We tag them with an Organization label (Partner_Type__c custom field) to distinguish them from client companies. This prevents partner records from appearing in sales pipeline views unless explicitly filtered. Additionally, we set the Organization's address, phone, and domain from Ziggu, and preserve the Ziggu company ID as Ziggu_Company_ID__c for reconciliation.