Migrate from Concord CRM to Twenty CRM

Concord CRM Companies map directly to Twenty CRM Companies. We export Companies first in the migration sequence because Concord Contacts reference company_id as a foreign key. The Concord company name maps to Company.displayName, domain maps to Company.domainName, and address fields map to Company.address with street, city, state, country, and postalCode parsed from the exported address string. Custom fields on Company migrate to custom fields on Twenty's Company object.

Concord CRM Contacts map to Twenty CRM People. The contact's email is the primary identifier used for deduplication during import. We resolve the company association by looking up the Concord company_id against the migrated Company records and populate CompanyMember on the Twenty People record. First name and last name split from the exported full name or name fields. Phone, email, job title, website, and all standard fields map to their Twenty equivalents.

Concord CRM Deals map to Twenty CRM Opportunities. The Concord dealstage maps to the Twenty Opportunity stage field, but stage names must be reconciled because Concord stages are free-text values exported from the pipeline configuration, and Twenty Opportunity stages are configured in workspace settings before import. We require the customer to configure matching stage names in Twenty before migration begins so that stage assignment lands correctly.

Concord CRM pipeline stages export as raw values (e.g., 'Qualified', 'Proposal Sent', 'Won', 'Lost'). Twenty CRM Opportunity stages must be pre-created in Settings with exact name matches. We generate a stage mapping table during scoping that the customer uses to create matching stages in Twenty. Probability percentages from Concord custom stage configuration map to stage probability fields in Twenty if available.

Concord CRM supports multiple deal pipelines. Twenty CRM uses a single pipeline model with stage-based progression. If the customer uses multiple pipelines in Concord, we map each pipeline to a Twenty Opportunity stage group or document the mapping for manual segmentation after migration. Multi-pipeline reporting in Concord will require rebuilding views in Twenty.

Concord CRM Products export with name, price, SKU, and description. These map directly to Twenty CRM Products with the SKU mapping to the product code field. Product records are independent of other objects in Concord and import straightforwardly. Price book and pricing information is a future-state consideration for Twenty's pricing model if the customer expands use.

Concord CRM Activities (calls, meetings, tasks) are reconstructed in Twenty as Task records for calls and tasks, and as Note records for meeting notes and standalone notes. We use the Concord activity linkedResourceType and linkedResourceId to reconstruct the association to the correct People or Company record in Twenty. The original activity date and notes body transfer to the Twenty record. Meeting invitations and attendee lists do not have a direct Twenty equivalent and are stored as Note body text.

Concord CRM custom fields use UUID as the API key and support boolean, date, select, text, and number types. Twenty CRM custom fields are created via the /metadata API. We create matching custom fields on the target object (People, Company, Opportunity, Product) before importing records, mapping the Concord field UUID and type to the Twenty field API name and data type. Select fields require value mapping if Concord uses picklist-style values.

Concord CRM Users and roles are not available via the standard export feature. We retrieve user data via the Concord API (email, name, role) for mapping purposes. Twenty CRM WorkspaceMembers are provisioned by email during workspace setup. We match Concord owners on email and flag any Concord owner without a matching Twenty WorkspaceMember for manual provisioning before record import.

Concord CRM workflows (trigger: Company/Contact/Deal created, Deal stage changed; actions: Create Activity, Send Email, Trigger Webhook) do not execute during data import and cannot be migrated as automation code. We audit every active Concord workflow during scoping and deliver a written inventory documenting the trigger, conditions, actions, and recommended Twenty workflow equivalent. The customer's admin rebuilds workflows in Twenty after migration. This applies to both Concord's native workflow engine and any webhook-based integrations.