Migrate from Concord CRM to Freshsales

Concord CRM Companies map directly to Freshsales Accounts. Concord's company name, domain, address, phone, industry, and custom fields translate to Freshsales Account fields. This object must migrate first because Concord Contacts reference company_id as a foreign key, and Freshsales Contacts require AccountId on import. We extract Companies via Concord's API (GET /api/v1/companies) or CSV export and load them before any Contact records.

Concord CRM Contacts map to Freshsales Contacts with AccountId resolved from the Concord company_id to the Freshsales Account ID. Concord contact fields (first name, last name, email, phone, title, website) map to Freshsales standard fields; Concord custom fields map to Freshsales custom fields of matching type. Contacts without a valid Concord company_id are imported with AccountId set to null, which Freshsales allows, and the customer's admin resolves these manually after migration.

Concord CRM does not have a separate Lead object; all prospects live as Contacts. During migration scoping, we determine which Concord Contacts should become Freshsales Leads versus Contacts based on the customer's qualification criteria (status field, has_deal flag, or custom field). We create a documented split rule during scoping so unqualified prospects enter Freshsales as Leads and can be converted to Contacts tied to Accounts at the appropriate pipeline stage.

Concord CRM Deals map to Freshsales Deals with deal name, value, expected close date, owner, and stage preserved. Concord deal stage names map to Freshsales pipeline stage names via a stage mapping table created during scoping. Concord custom fields on Deals map to Freshsales Deal custom fields. Deals without a Contact association in Concord are imported without a ContactId, which Freshsales permits, and the admin can link them post-migration.

Concord CRM pipeline stages (stage name, probability percentage, display order) map to Freshsales pipeline stage values. If the customer uses multiple Concord pipelines, we map each to a separate Freshsales pipeline. Stage probabilities in Concord are stored as decimal values (0.00 to 1.00) and convert to Freshsales percentages (0 to 100). We configure Freshsales pipeline stages before Deal migration begins.

Concord CRM Products (name, price, SKU, description) map directly to Freshsales Products. Product migration has no foreign-key dependencies on other objects, so it can run in parallel with Companies. Concord product pricing (regular price, sale price) maps to Freshsales standard cost and selling_price fields.

Concord CRM Activities (calls, meetings, tasks) split into Freshsales Tasks (calls and tasks) and Appointments (meetings). Concord activity type (call, meeting, task) determines the destination object. Concord activity notes migrate as the task or appointment description. Concord linked_resource_type and linked_resource_id allow us to reconstruct the association back to the parent Contact or Deal in Freshsales via ContactId or DealId.

Concord CRM custom fields (boolean, date, select, text, number) map to Freshsales custom fields of equivalent type. Boolean custom fields in Concord (stored as 0/1) map to Freshsales checkbox fields. Select (dropdown) fields map to Freshsales dropdown fields with values preserved. We pre-create Freshsales custom fields before migration begins using the Freshsales API. Concord custom field UUIDs are used only on the source side; Freshsales custom fields are created with display names matching the Concord field label.

Concord CRM Users (email, name, role) map to Freshsales Users. Concord owner_id on Contact, Company, Deal, and Activity records resolves to Freshsales User by email match. Any Concord User without a matching Freshsales User is held in a reconciliation queue; the customer's Freshsales admin provisions missing Users before record import resumes. Role assignments in Concord are documented for manual reconstruction in Freshsales permissions settings.