Migrate from Twenty CRM to Zoho CRM

Twenty Company records map directly to Zoho CRM Accounts. Company.domain becomes the Account Website field and serves as the dedupe key during import. Zoho Accounts must be created first because both People (as Contacts) and Opportunities carry foreign key dependencies that require an existing parent Account. We pre-create the Zoho Account schema, including all custom fields matched from Twenty, before any dependent records are loaded.

Twenty People map to Zoho Contacts by default. If the customer uses Twenty's lifecycle stage or tag properties to track prospect qualification status, we apply a split rule during migration: unqualified prospects (no Opportunity attached, no recent engagement) map to Zoho Lead; qualified records map to Contact attached to the previously created Account. Email serves as the dedupe key. The original Twenty record ID is preserved in a custom field twenty_record_id__c for audit traceability.

Twenty Opportunities map to Zoho Opportunities. The Opportunity stage from Twenty maps to a Zoho Stage value; if the stage names differ, we create a Zoho pipeline with matching stage labels before migration. Closed-Won and Closed-Lost reasons from Twenty custom fields migrate to Zoho Loss Reason and Won Reason picklists. AccountId is resolved to the previously created Zoho Account before Opportunity insert.

Twenty Tasks map to Zoho Tasks. The related record (People, Company, Opportunity) is resolved to the corresponding Zoho Contact, Account, or Opportunity ID at migration time. Task Status, Priority, Due Date, and assignee (Owner) migrate directly. Any Twenty tasks without a resolvable parent record are held in a reconciliation queue for the customer to resolve before final import.

Twenty Notes migrate to Zoho Notes linked via the Zoho CRM Notes module to their parent record (Contact, Account, or Opportunity). Note body content and title transfer directly. Attachments in Twenty migrate as Zoho Attachments linked to the corresponding record. Note ordering in the timeline is preserved by setting the Zoho Note creation date to the original Twenty timestamp.

Twenty Custom Objects map to Zoho CRM Custom Modules. Files named with a _C suffix (e.g., Rockets_C.csv) are auto-recognized by Zoho's Data Migration wizard as custom modules and created during migration; files without the suffix are mapped manually during the module mapping step. We pre-create the Zoho custom module schema, including all custom fields and lookup relationships, before any data import. Zoho enforces a 300-field-per-module limit and 5-lookup-field-per-module limit that we validate against Twenty's custom object field count during scoping.

Twenty Owner references on People, Companies, Opportunities, and Tasks are resolved by email match against Zoho CRM Users. Any Twenty Owner without a matching Zoho User is flagged in a reconciliation queue before migration begins; the customer's Zoho admin provisions the missing User before record import resumes. OwnerId references on Opportunities and Tasks are resolved at migration time using the validated User mapping.

Twenty's engagement email records (where present via third-party connectors) map to Zoho Email Messages linked to the parent Contact, Account, or Opportunity. Email content, subject, and timestamp migrate directly. Note that Twenty lacks native two-way email sync, so historical email engagement data may be incomplete or absent in Twenty; we flag this gap during scoping so the customer understands the activity timeline ceiling before migration.

Call records from Twenty (where present via third-party integrations) map to Zoho Call Logs linked to the parent Contact, Account, or Opportunity. Call duration, disposition, and recording URL migrate to Zoho call log fields. Similar to email, native call logging is absent from Twenty, so the completeness of call history in the destination depends on whether a third-party connector was actively logging calls in Twenty.

Twenty's soft-delete uniqueness constraint means that importing a record with the same email (for People) or domain (for Companies) as a soft-deleted record will restore that deleted record instead of creating a new one. We detect soft-deleted records during scoping and coordinate with the customer on whether to permanently purge deleted records in Twenty before export or map incoming records to the restored counterparts. This decision is made before migration begins to prevent duplicate or unexpected record behavior in Zoho.