Migrate from Concord CRM to Zoho CRM

Concord CRM Company records map directly to Zoho CRM Account. The Company must be exported and imported before Contact because Zoho Accounts are the parent record for Contacts via the Account Name lookup field. We extract the company_id, company_name, website, phone, address, and any custom fields from Concord's Companies endpoint or CSV export and map them to the corresponding Zoho Account fields. If the Concord Company has a primary contact flag, we carry that forward for Contact sequencing.

Concord CRM Contacts do not distinguish between unqualified prospects and qualified buyers; Zoho CRM separates Leads (unqualified) from Contacts (qualified, attached to Accounts). We apply a split rule during scoping based on the customer's Concord CRM data: Contacts with no associated Deals and no sales activity history typically map to Zoho Lead; Contacts with active Deals or recent task/logged activities map to Zoho Contact attached to the corresponding Account. The original Concord contact_id is preserved in a custom field concord_original_id__c for reconciliation. If the customer has no lead-conversion process, all Concord Contacts can map directly to Zoho Contacts attached to Accounts.

Concord CRM Deals map to Zoho CRM Potentially-custom module or standard Deals module depending on the customer's Zoho edition configuration. Concord deal fields (deal_name, amount, expected_close_date, stage, owner) map to Zoho Potentially-custom module or Deal Name, Amount, Closing Date, Stage, and Owner. Concord pipeline stages are exported as raw stage names or IDs and must be mapped to Zoho Pipeline stage values that we configure before import. We flag any Concord Deals without a valid associated Contact or Company for manual review before insertion.

Concord CRM pipeline stages are stored as deal properties and export as stage names or IDs. We map each Concord stage to a Zoho Pipeline stage with a corresponding probability percentage. If the customer has multiple Concord pipelines, we create multiple Zoho Potentially-custom module or Potentially-custom module pipelines, each with its own stage sequence. Stage mapping is validated against the customer's Concord stage names during scoping.

Concord CRM Products (name, price, SKU, description) map directly to Zoho CRM Products. Products are independent of other objects in Concord and migrate straightforwardly. We map product_name to Product Name, price to Unit Price, sku to Product Code, and description to Description. Price book entries in Zoho are created during the migration to support Deal product line items if the customer uses product-linked Deals.

Concord CRM Activities (calls, meetings, tasks) export with type, date, notes, and linked resource ID. We reconstruct the association by resolving the linked resource type (Contact, Company, Deal) and ID to the migrated Zoho record's ID. Calls and general tasks map to Zoho Tasks with Task Type set to Call or Task respectively; meetings map to Zoho Events with Start Date Time, End Date Time, and Location preserved. Concord activity timestamps are preserved as Activity Date in Zoho for timeline ordering. Note: Concord CRM does not export email engagements as a distinct activity type; emails are typically stored as activity notes rather than structured records.

Concord CRM custom fields (boolean, date, select, text, number) export with the field UUID as the key in the request payload. We map these to Zoho CRM custom fields created in the respective module before migration. Zoho custom fields require paid edition access (not available in Free edition) and are subject to field limits per module per edition. We confirm the customer's Zoho edition during scoping and create all custom fields before any data import begins. Boolean fields from Concord map to Zoho Checkbox; date fields map to Zoho Date; select fields map to Zoho Picklist with matching values.

Concord CRM Users export via API with email, name, and role assignment. We resolve Concord users by email match against the Zoho CRM destination's User table. Owners referenced on Concord Deals and Contacts map to Zoho Owner by email. Any Concord user without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role permissions from Concord are documented but must be manually reconstructed in Zoho Profiles and Permission Sets.

Concord CRM Workflows (trigger: Company/Contact/Deal created, Deal stage changed; action: Create Activity, Send Email, Trigger Webhook) do not execute during data import. We do not migrate workflows as code. We audit all active Concord CRM workflows during scoping, document the trigger conditions, actions, and intended logic, and deliver a written workflow inventory with recommended Zoho Workflow Rules equivalents. The customer's admin rebuilds these manually in Zoho's Workflow Rules builder post-migration. This is a manual scope item outside the data migration scope.

Concord CRM does not include a document attachment export feature in the standard export tool or API. Attachments stored in the application's storage/app directory must be manually extracted via file system access (FTP/SFTP) and transferred. We document the storage directory structure, list all attachment files with their associated record IDs, and provide the customer with a file-transfer playbook. Attachments are then manually reattached in Zoho CRM under the Documents module or linked via Zoho WorkDrive. This is a manual scope item outside the automated data migration scope.