Migrate from Ziggu to Twenty CRM

Ziggu Clients map directly to Twenty CRM People. Each Client record carries name, email, phone, and company association — these translate to People.name, People.emails.primary, People.phone, and People.companyId. Original client IDs preserved as custom field Source_Client_ID__c for delta-run de-duplication. Email addresses populate the emails array with the primary flag set, and any secondary phone numbers map to additional phone entries on the People record.

When a Ziggu Client record includes a company name field (companyName or similar), that value splits into a new Twenty CRM Company record with the person linked via companyId. If no company name exists, the person links to a default 'Individual Client' placeholder Company record to satisfy Twenty CRM's required companyId on People.

Ziggu Projects translate to Twenty CRM Opportunities. Project.name becomes Opportunity.name; project total value or unit prices sum into Opportunity.amount; project status (Inquiry/Reservation/Contract/Works/Handover) maps to Opportunity.stage values. Your team defines the stage pick-list before migration — FlitStack generates the value-mapping plan.

Ziggu Units within a Project split into separate Twenty CRM Opportunities when each unit represents an independent deal (separate buyer, separate price). Units with shared buyer and price aggregate into a single Opportunity with amount = unit count × unit price. FlitStack surfaces the splitting logic in the pre-migration plan so your team confirms the rule before data moves.

Ziggu project lifecycle stages (Inquiry, Reservation, Contract, Works, Handover) map to Twenty CRM Opportunity Stage values. Each source stage name maps to a target stage name via a value-map. Probability and forecast category re-applied from Twenty CRM's stage setup. Stage-transition timestamps preserved as custom datetime fields Stage_Entered_Date__c.

Ziggu Tasks map 1:1 to Twenty CRM Tasks. Task.title → Task.title; Task.dueDate → Task.dueDate; Task.assignee email resolves to Twenty CRM workspace member by email match. Tasks linked to a Project attach to the migrated Opportunity; Tasks linked to a Client attach to the migrated People record.

Ziggu Documents attached to Projects or Clients download and re-upload to Twenty CRM as Files on the corresponding Opportunity or People record. Documents with text content (specifications, briefs) migrate as Twenty CRM Notes with the file linked as an attachment. File size and format compatibility checked against Twenty CRM limits before migration.

Ziggu Conversation messages migrate as Twenty CRM Notes on the linked People record. Each message becomes a separate Note with timestamp, sender, and message body. Original conversation threading is not preserved — messages appear as sequential notes ordered by creation date. Conversation metadata (read/unread status) does not migrate as Twenty CRM has no equivalent.

Ziggu Financials module (payment schedules, invoices, balances) translates to custom Number, Currency, or Date fields on Twenty CRM Opportunity. Payment status, amount paid, and balance due become custom fields: Z_Payment_Status__c, Z_Amount_Paid__c, Z_Balance_Due__c. Invoice line items require a custom Invoice_Lines__c relation object if granular detail must be preserved.

Ziggu Surveys module translates to a Twenty CRM custom object (Survey_Response__c) with custom fields matching each survey question. Respondent email links to the People record via email match. Survey scores and NPS values become Number fields. Multi-question surveys create a one-to-many relationship (one People record → many Survey_Response__c records).

Ziggu Sales module (leads, reservations, contracts) maps to Twenty CRM Opportunities with custom fields capturing reservation status and contract terms. Reservation date becomes Z_Reservation_Date__c; contract signed flag becomes Z_Contract_Signed__c (checkbox). Pipeline stage handles the overall progression — the Sales add-on fields augment rather than replace the standard Opportunity object.

Ziggu team member email addresses resolve against Twenty CRM Workspace Members by email match. Unmatched owners are flagged before migration — your Twenty admin either creates a matching workspace member or assigns those records to a fallback owner. No record lands without a valid Twenty CRM assignee.