Migrate from Sage CRM to Zoho CRM

Sage CRM Companies map directly to Zoho CRM Accounts. The CompanyName, Address fields, Industry, and Classification data migrate as-is. Company is the parent entity in the Sage CRM foreign-key chain, so we export and import Accounts first before any dependent entities (Contacts, Opportunities, Cases) so that the Zoho Account ID is available for lookups. Sage CRM Company Type and Status map to Zoho Account Type and Account Site fields. Custom Company fields migrate as standard Zoho custom fields.

Sage CRM Contacts link to Companies via PrimaryCompanyLink. We export all Contact fields including custom fields, resolve the PrimaryCompanyLink to the Zoho Account ID produced by the Account import, then insert the resolved Account ID during Contact import. Duplicate detection uses email address as the dedupe key in Zoho. Any Contact without a matching Account is held in a reconciliation queue; the customer resolves the orphaned Contact before it imports, or the Contact imports without an Account association and is flagged for manual linking post-migration.

Sage CRM Leads have their own lifecycle stages, qualification fields, and source tracking that map to Zoho CRM Lead Status, Lead Source, and Rating fields. Unlike HubSpot, Sage CRM does not use a Lead-versus-Contact split at the entity level, so Lead maps 1:1 to Zoho Lead without a conversion step required at migration time. Custom Lead fields migrate as Zoho custom fields with type preservation (picklist, date, numeric, text). The customer's Sage CRM lead stage values are mapped to Zoho Lead Status picklist values during schema design.

Sage CRM Opportunities map to Zoho CRM Deals. The OpportunityName or related CompanyName becomes the Deal Name. Stage maps from Sage CRM oppo_stage to Zoho Stage Name. Expected Close Date and Amount migrate directly. Owner assignment resolves via email match to Zoho Users in the same way as Contacts. Custom Opportunity fields migrate as Zoho Deal custom fields. Multi-currency amounts in Sage CRM use the CurrencyKey field; we migrate the numeric amount and note the currency in a custom field if Zoho Multi-Currency is not enabled.

Sage CRM Cases map to Zoho CRM Cases with severity, status, and assignment fields preserved. The Case subject, description, and resolution notes migrate as Zoho Case Subject, Description, and Solution fields. Owner assignment resolves via email match. Case status values (New, Open, Pending, Resolved, Closed) map to Zoho Case Status picklist values. Case-related Communication records are handled separately in the Communication mapping.

Sage CRM Communication records are entity-type agnostic, linked to Companies, Contacts, Leads, Opportunities, or Cases by comm_entity-type and comm_entityid. During transform, we split the Communication table by comm_entity-type: emails become Zoho Email records linked to the parent record; call logs become Zoho Call records; meetings become Zoho Event records; generic notes become Zoho Task or Note records. The parent Zoho record ID is resolved at migration time using the target entity type and the original comm_entityid mapped to the Zoho record. This split is the most complex part of a Sage CRM migration and is performed as a separate transform job before any Communication data is loaded.

Sage CRM Custom Entities have internal API names that differ from their UI display names (e.g., CustomEntityProjects vs the UI label 'Projects'). We inspect the Sage CRM REST API entity model to retrieve all Custom Entity definitions, their internal names, field schemas, and lookup relationships before migration scoping. Each Custom Entity becomes a Zoho Custom Module. Files with _C suffix in the Sage export filename can auto-create modules in Zoho's Data Migration wizard, but we pre-create the schema via Zoho API to control field types and avoid the picklist-vs-free-text mapping issues that auto-creation causes.

Sage CRM Users export with role-based security profiles. User accounts map to Zoho Users by email address match. Sage CRM role names (e.g., SalesRep, SystemAdmin) map to Zoho Profiles (Standard, Administrative) during scoping. The customer's Zoho admin provisions User accounts before migration; any Sage CRM user without a matching Zoho User goes to the reconciliation queue. Active vs inactive status is preserved in a custom Zoho field so the admin can batch-enable accounts post-migration.

Sage CRM reports store field references by internal database IDs and formatting rules that are not portable. We export the report metadata (report names, descriptions, and field lists) as a written document. Zoho CRM Reports are rebuilt from scratch using Zoho's report builder and Zoho Analytics for multi-module reporting. The report inventory document is delivered to the customer's admin with screen-by-screen rebuild instructions.

Sage CRM workflow rules are database records containing ASP-scripted actions and escalation triggers that cannot be extracted as portable automation logic. We produce a complete workflow inventory documenting every active Sage CRM rule: trigger event (e.g., case created, opportunity stage changed), condition criteria, action sequence, and escalation path. This inventory is handed to the customer's Zoho admin to rebuild in Zoho Blueprint (multi-step process) and Zoho Workflow Rules (event-triggered actions). Workflow rebuild is outside the migration scope and is a separate engagement or internal admin task.