Migrate from Concord CRM to Salesforce Sales Cloud

Concord CRM stores contacts with a flat company_id foreign key pointing to a Companies record. Salesforce does not have a direct equivalent of this flat model. We split Concord contacts into Salesforce Leads and Contacts based on a rule defined during scoping: contacts without an assigned company or with a prospect status map to Lead; contacts with an assigned company map to Contact and get linked to an Account via AccountId Lookup. The original Concord company_id is preserved in a custom field concord_company_id__c on the Contact for reconciliation audit. Concord does not have a separate Lead object, so the split is a pure transformation at migration time rather than a conversion.

Concord Companies map directly to Salesforce Account. Company name becomes Account Name, domain becomes Website, and industry fields map by type. Concord's company_id is preserved as a custom field concord_company_id__c on Account to support the Contact lookup resolution during Contact migration. Accounts must be imported before Contacts because the Contact migration requires AccountId to be resolved before insert. If Concord contacts reference a company_id with no matching Concord Company record, we hold those contacts in a reconciliation queue for the customer to decide: create a placeholder Account or convert those contacts to Leads.

Concord Deals map to Salesforce Opportunity. The Concord dealstage value maps to a Salesforce StageName that we configure during pipeline setup. Closed-Lost reason and Closed-Won reason from Concord custom fields become Salesforce Loss Reason and Won Reason fields. Concord's assigned user maps to Salesforce OwnerId via email matching against the destination User table. If Concord supports multiple pipelines (enterprise extension), each pipeline maps to a Salesforce Opportunity Record Type with its own Sales Process whitelist.

Concord Products map to Salesforce Product2 records with Standard Price Book entries created during migration. Concord SKU (hs_sku equivalent) maps to ProductCode. Price, name, and description migrate directly. Product2 must be created and a Pricebook2 activated before any OpportunityLineItem records reference them.

Concord call activities map to Salesforce Task with TaskSubtype set to Call. Call disposition, duration, and notes preserve in custom Task fields. The linked resource type and resource_id from Concord determine the WhatId on Task: if the Concord call was linked to a Deal, the WhatId points to the migrated Opportunity; if linked to a Contact or Company, the WhatId resolves after Contact and Account migration completes. ActivityDate is set to the original Concord timestamp to preserve timeline ordering.

Concord meeting activities map to Salesforce Event. StartDateTime, EndDateTime, and Location migrate directly. Attendee information from Concord's linked resources resolves to EventRelation records pointing at the migrated Contact, Lead, or User records. If the Concord meeting was linked to a Deal, WhatId points to the migrated Opportunity after Opportunity migration completes.

Concord task activities map to Salesforce Task with Status, Priority, and ActivityDate preserved. Task subject and body migrate as-is. The task assignment resolves by matching the Concord assigned user to the migrated Salesforce OwnerId via User email lookup. Concord's linked resource type and ID determine WhatId resolution, which is deferred until Account and Opportunity migration complete.

Concord notes with a linked resource type and ID map to Salesforce Note records linked via ContentDocumentLink to the parent Lead, Contact, Account, or Opportunity. Note body migrates as rich text. The parent record lookup resolves after the relevant object migration completes, using the concord_resource_type and concord_resource_id fields to route each note to the correct destination record.

Concord CRM custom fields use UUID as the API key in request payloads, with different payload formats for boolean, date, select, text, and number field types. We map each Concord custom field to a Salesforce custom field of equivalent type: text fields become Text(255) or Long Text Area, dates become Date, selects become Picklist or Multi-Select Picklist, numbers become Number. Custom field API names in Concord may not match Salesforce __c naming conventions, so we normalize during schema design. Concord custom fields are discovered during scoping and the destination custom fields are pre-created in Salesforce before any data import.

Concord CRM Users export via REST API with email, name, and role. We match by email against the Salesforce destination org's User table. Any Concord User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record migration resumes. Role permissions from Concord (such as export permission) do not map to Salesforce profiles or permission sets; we document them as a manual rebuild item for the customer's admin.

Concord CRM stores deal stages as values attached to the deal pipeline. We map each Concord stage name to a Salesforce StageName value within a Salesforce Sales Process. Stage probability percentages migrate from Concord to Salesforce StageProbability. Multiple Concord pipelines (if used via enterprise extension) map to Salesforce Opportunity Record Types with separate Sales Process configurations per Record Type.

Concord CRM does not include a document attachment export feature in the standard export tool or REST API. Attachments stored in the application file system (storage/app directory) cannot be retrieved through the documented export interface and require manual file system access via the hosting server. File attachments are excluded from migration scope and flagged in the documentation for manual retrieval post-migration. If the customer requires attachment migration, a separate file system export step coordinated with the Concord hosting administrator is required outside standard migration scope.