Migrate from Zoho CRM to Twenty CRM

Zoho Leads map to Twenty Person records. We extract Lead_Status, Lead_Source, and any custom fields and store them as Twenty Person fields or custom fields created via the /metadata API before import. The Zoho Lead-to-Contact conversion logic does not apply in Twenty; all imported Leads become Persons directly without a conversion step.

Zoho Contacts map to Twenty Persons. The Contact-to-Account relationship in Zoho maps to the Person's relationship with a Twenty Company record. We sequence Company import before Person import so that the Company link resolves at insert time rather than requiring a follow-up update pass.

Zoho Accounts map directly to Twenty Companies. We use the Account_ID as the external identifier for deduplication and preserve the account's industry, website, phone, address, and any custom fields. Multi-address accounts in Zoho are stored as separate address records; we collapse the primary address into the Company record and store additional addresses as custom fields or note attachments.

Zoho Deals map to Twenty Opportunities. The Opportunity's link to a Company (Account) must resolve before Opportunity insert. We map Zoho's dealstage and pipeline to Twenty's pipeline stage field and handle multi-pipeline setups by creating separate pipeline configurations in Twenty before migration begins.

Zoho Products map to a Twenty Product custom object created via the /metadata API before migration. Product_Code, Unit_Price, and Quantity_Unit migrate as fields. Products must import before any Quote or Sales Order migration because line items reference products by ID.

Zoho nests line items as related records rather than inline fields. Standard CSV exports drop subform rows entirely. We issue separate API calls for each subform relationship (Quotes/Products, SalesOrders/Products), reconstruct the parent-child hierarchy, and upsert both layers into Twenty with the lookup resolved at insert time. If the source Zoho plan lacks API access, we alert the customer that subform data will require manual re-entry.

Zoho Tasks, Events, and Calls map to Twenty Activity records. We preserve the linked-to-record association by resolving the WhoId (Person) and WhatId (Opportunity, Company) references at migration time. Activity timestamps are set from the original Zoho created_at value, not the import date, to preserve the timeline ordering sales reps rely on.

Zoho Notes migrate to Twenty Note records. We resolve the parent record link (Person, Company, or Opportunity) and write the note body as rich text. Notes attached to multiple records create multiple Note entries rather than a single shared note.

Zoho attachments are stored as separate file records linked to parent modules. They do not appear in CSV exports and must be fetched via the Attachments API endpoint. We download files, upload them to Twenty's file storage, and create the attachment link record pointing to the parent Person, Company, or Opportunity. File size limits and storage provisioning are confirmed before migration begins.

Zoho custom modules migrate to Twenty custom objects. We introspect the custom module's field metadata via GET /settings/fields in Zoho, create the equivalent Twenty object via the /metadata API, and then import the data. Schema varies per tenant; custom field types (picklist, multi-select, date, currency) are mapped to their Twenty equivalents. Custom module discovery is always the first step in the migration plan because downstream objects may have lookups to custom modules.

Zoho User records carry name, email, role, and territory. We extract Users during discovery and build an email-to-ID mapping table. At migration time, we either match by email to an existing Twenty workspace user or flag missing users for the customer's admin to provision before record import resumes. Inactive Zoho users assigned as record owners are reassigned to an active admin user to avoid orphaning records.