Migrate from Zoho CRM Plus to Twenty CRM

Zoho Leads map to Twenty Person records that function as leads before qualification. We set a custom field zoho_lead_id__c and zoho_lead_status__c to preserve the original Zoho Lead_Status and any lead scoring values. Once the customer defines the qualification criteria (e.g., booking a demo moves a Person to an Opportunity), the admin creates a matching filter in Twenty. Unqualified leads are imported as Person records; leads that should be companies are imported as Organisation records with the Person linked as a primary contact.

Zoho Accounts map directly to Twenty Organisation. The Zoho Industry, Website, Address, Phone, and Annual_Revenue fields map to their Twenty equivalents. Organisation is the parent of any related Person records, so we import Accounts first to satisfy the Organisation lookup before any Contact import. We deduplicate by Zoho Account ID stored as zoho_account_id__c for future sync or rollback.

Zoho Contacts map to Twenty Person records. We resolve the parent Organisation by matching Zoho Account_ID to the zoho_account_id__c field on Organisation records created in the previous phase. Contact Role on Deals migrates as a custom field opportunity_role__c on Person since Twenty does not have a native Contact Role object. Tags on Zoho Contacts migrate as a comma-separated custom field original_tags__c.

Zoho Deals map to Twenty Opportunities with Stage, Amount, Closing_Date, and Probability preserved. We map the Zoho pipeline to a single Twenty pipeline and confirm stage names with the customer during scoping since Zoho pipeline stage names vary per org. Closed-Won and Closed-Lost outcomes and their reasons migrate as custom fields. Deal_Name becomes the Opportunity name; if the Deal has no linked Account, we link it to the primary Organisation on the Deal's Contact.

Each Zoho pipeline stage becomes a Twenty pipeline stage with a probability percentage. We ask the customer to confirm the stage map during scoping since Zoho allows custom stage names and probabilities per pipeline. The migration sets probability values on each stage to match Zoho's stage-level probabilities.

Zoho Tasks and Events map to Twenty Activity records. We preserve the original Zoho Created_Time as a custom field original_created_at__c since Twenty's native create_date is set at import time. Activity assignment resolves Zoho Owner email to Twenty User by email match. Call Logs migrate as Activity with type set to call and duration preserved in a custom field.

Zoho Campaigns do not have a direct Twenty CRM equivalent. We import Campaigns as a custom object with fields for campaign name, type, status, start date, end date, budget, and expected revenue. The admin maps Campaign membership to Opportunity custom fields or uses Twenty's grouping capabilities for reporting. If the customer uses Zoho Campaigns heavily for attribution, we discuss whether to import as a custom object or map to Opportunity-level campaign fields during scoping.

Zoho Desk cases inside CRM Plus migrate to Twenty Case records. We preserve case status, priority, channel, assignee (by email), and the related Contact or Account. Comment threads migrate as Case comment entries in chronological order. Zoho's SLA fields map to custom fields in Twenty since SLA management is not native to the core plan.

Zoho Products map to a Twenty custom object named Product. We create the schema before migration: product code, name, unit price, tax, and description migrate as typed fields. Product bundles and product relationships are documented separately for the admin to rebuild in Twenty's product linking setup.

Zoho custom modules migrate to Twenty custom objects of matching name. We inspect the Zoho custom module schema via the API before migration to identify all field types (text, lookup, picklist, currency, date, number). Each field type maps to an equivalent Twenty field type, with lookup fields resolved by querying the target object and storing the Twenty record ID as a foreign key. Picklist values are imported as text or enum depending on Twenty's field support at migration time.

Zoho Users migrate as Twenty Users. We match by email address. Any Zoho user who is inactive or has left the organisation is set to inactive in Twenty. Ownership of Zoho Deals and Activities resolves via the email-to-User lookup, and records are assigned to the matching Twenty User on import.

Zoho attachments on Deals, Contacts, Accounts, and Cases are exported from Zoho WorkDrive to cloud storage (S3 or equivalent) and linked back to the destination Twenty records via URL reference or file attachment API. We flag any attachment exceeding 25 MB for manual handling since Zoho's attachment handling for very large files requires WorkDrive API access and may need compression before re-upload. Storage quota is verified against Twenty's configured cloud provider before migration begins.