Migrate your Zoho CRM Plus data

Standard Zoho CRM object with well-documented fields and lifecycle stages. We map Leads 1:1 to the destination Lead or Contact object, preserving Lead_Status and conversion tracking data as custom properties where the destination lacks a native Lead object.

Accounts in Zoho store company records and are the parent object for Contacts and Deals. We map Accounts to the destination Companies/Accounts object, preserving industry, website, address, and billing fields. Multi-currency support in Zoho is preserved at the field level.

Contacts in Zoho link to Accounts and hold person-level data. We map Contacts 1:1 to the destination Contacts object, preserving ownership, custom fields, and the Contact Role on related Deals. Tags on Contact records are migrated as tag strings or custom fields depending on destination schema.

Deals represent pipeline opportunities linked to Accounts or Contacts. We map Deals to the destination Deals or Opportunities object, preserving stage, amount, closing date, probability, and pipeline assignment. Zoho's Deal history (stage changes) is preserved as Activity records.

Zoho allows multiple pipelines per module and custom stage names. Stage names and probabilities vary between Zoho orgs. We ask customers to confirm the destination pipeline stage map during scoping to avoid mismapping. Custom stage colours and icons do not transfer.

Activities include Tasks, Events, and Call Logs. We map these to the destination Activities or Tasks/Events object, preserving the related-to record (Contact, Account, Deal), due date, status, and owner. Recurring Activities are preserved as individual records.

Campaigns in Zoho track marketing initiatives and link to related Leads and Contacts. We map Campaigns to the destination Campaigns object, preserving type, status, start/end dates, budget, and expected revenue. Campaign member tracking (who responded) is migrated as campaign member records.

Cases are handled via Zoho Desk within CRM Plus. We map Cases to the destination Tickets or Cases object, preserving status, priority, channel, assignee, and the related Contact or Account. Comment threads and internal notes are migrated as conversation records. SLA configurations are documented but not ported as they are system-level settings.

Products in Zoho store the product catalogue with pricing information. We map Products to the destination Products object, preserving product code, unit price, tax, and description. Product bundles are preserved as line items linked to the parent product.

Zoho stores these as separate modules. We map each 1:1 to the destination equivalent object, preserving line items, totals, tax, discount, and related Account, Contact, and Product links. Status fields (Draft, Sent, Paid) are preserved as-is.

Zoho allows custom modules via the Custom module in CRM. We map custom modules by inspecting the schema via the API before migration. Custom field types (lookup, picklist, currency, date) are converted to the nearest matching destination type. Relationships between custom modules and standard objects require explicit mapping during scoping.

Zoho supports custom fields on every standard module. During migration, we create equivalent custom fields in the destination if they do not exist. Autonumber and Formula fields cannot be created during migration (Zoho's own wizard also notes this limitation). Picklist values are preserved exactly; we flag any that exceed the destination field's character limit.

Zoho Users include name, email, role, profile, and territory assignment. We map Users to the destination Users object, preserving active/inactive status and role. Ownership of records (Contacts, Deals, etc.) is remapped by matching email addresses; if a destination user does not exist for a Zoho owner, we reassign to the migration admin or a designated placeholder user.

Zoho supports tagging on Contacts, Accounts, Deals, and other records. Tags are migrated as tag strings or a dedicated Tags object depending on destination capability. Zoho's own migration wizard explicitly confirms tags are migratable, and we honour that same path.

Zoho stores Attachments on records and in the Document Library. We export attachments to cloud storage (S3 or equivalent) and link them back to the destination records via URL or file reference. Large attachments (>25 MB) may require chunked upload handling. The Document Library is migrated as a flat file set or into the destination's document management module.