Migrate from FIVE CRM to Zoho CRM

FIVE CRM separates Contacts from Leads, while Zoho CRM uses a Leads module that can optionally be split into Contacts tied to Accounts for qualified records. We map the FIVE CRM Lead_Source field to a Zoho CRM custom field original_lead_source__c, and we preserve any lead score from FIVE CRM as a custom field lead_score__c on the Zoho Lead. The decision to convert Leads to Contact+Account in Zoho depends on whether the customer's FIVE CRM Leads represent unqualified prospects or a parallel pipeline that should remain separate. We confirm this split rule during the pre-migration field mapping session.

FIVE CRM Companies map directly to Zoho CRM Accounts. The company name becomes Account Name, and the domain or website URL maps to the Account Website field. We use Account Name as the dedupe key during import. Account must be imported before Contact to satisfy the Parent Account lookup on the Contact record.

FIVE CRM Lead records map to Zoho CRM Leads 1:1. Any FIVE CRM lead score custom field becomes a numeric custom field on the Zoho Lead. Lead status in FIVE CRM maps to Zoho CRM Lead Status with a mapping table agreed upon during scoping because FIVE CRM status values vary by tenant configuration.

FIVE CRM Deals map to Zoho CRM Potentials. The deal amount, stage, and close date migrate directly. We map FIVE CRM deal stage names to Zoho CRM Potential Stage values using a stage mapping table built during scoping. If FIVE CRM uses a custom stage label not available in Zoho, we create a custom Stage picklist value in Zoho before import.

FIVE CRM Pipelines with their custom stage names map to Zoho CRM Pipeline configurations. Each FIVE CRM pipeline becomes a Zoho Pipeline with Stage values configured to match the source stage labels. We note that Zoho CRM Pipeline is a reporting grouping concept rather than a record type, so multi-pipeline FIVE CRM accounts need their deals tagged with a pipeline name field for segmentation after migration.

FIVE CRM Campaigns map to Zoho CRM Campaigns at the membership level. We migrate campaign name, type, status, and start/end dates. Campaign membership (which Contacts were added to which Campaigns) migrates as Zoho Campaign Member records linked to the corresponding Leads. Per-contact engagement flags (opted-in, replied, etc.) migrate to custom fields on the Campaign Member record. FIVE CRM campaign-level email engagement logs (opens, clicks, replies) do not migrate as granular event records because Zoho Campaign does not store per-event logs at the same level of detail.

FIVE CRM Tasks with due dates, assignees, subjects, and completion status map to Zoho CRM Tasks. Task type variants (Call, Email, Follow-up) in FIVE CRM map to Zoho custom picklist values on a task_type__c custom field because Zoho Tasks do not natively distinguish task subtypes the way FIVE CRM does.

FIVE CRM relies heavily on custom fields to capture telemarketing-specific data (call dispositions, dialer statuses, warm-up flags, lead quality ratings). Every custom field requires explicit type mapping during the pre-migration field mapping session because FIVE CRM does not expose a public schema document via its API. We enumerate each custom field, confirm its data type (text, number, date, picklist, checkbox), and agree on the destination Zoho CRM custom field name and type before any data moves. Skipping this step leads to silent type coercion or dropped values.

FIVE CRM Tags used for contact segmentation and campaign targeting map to Zoho CRM Tags on the Lead or Contact record. If the customer uses tags for data classification rather than segmentation, we offer the alternative of mapping them to a Multi-Select Picklist field on the Contact/Lead layout. The customer chooses the tag strategy during scoping because Zoho Tags and Multi-Select Picklists behave differently in filters and reports.

File attachments associated with Contacts, Companies, or Deals migrate via file reference re-upload to Zoho CRM Attachments. Attachments over 10MB require separate handling due to standard API size limits. We flag large attachments during the pre-migration audit and handle them as a separate import phase with explicit file reference mapping.

FIVE CRM Users map to Zoho CRM Users by email match. Any role or permission differences between the two platforms require manual reassignment in Zoho after migration. We extract every distinct FIVE CRM owner referenced on Contacts, Companies, Deals, and Tasks, match by email against the destination Zoho org, and flag any owners without a matching Zoho User for the customer's admin to provision before record import.