Migrate your Concord CRM data

Contacts export with all standard fields plus custom fields via CSV/XLSX. API supports CRUD operations using the contact's ID. We map the contact's company association from the exported company_id to preserve the parent-child relationship in the destination CRM.

Companies export cleanly with all standard and custom fields. Must be exported first in migration sequencing because Contacts reference company_id as a foreign key. API supports full CRUD with Bearer token auth.

Deals export with stage, value, expected close date, and assigned user. Pipeline stages export as raw values that require mapping to the destination pipeline's stage names. API supports create/update/delete operations.

Products export with name, price, SKU, and description. Not tied to other objects via foreign key constraints, so migration is straightforward. API supports standard CRUD operations.

Activities (calls, meetings, tasks) export with type, date, notes, and linked resource ID. We reconstruct the association back to the parent Contact, Company, or Deal using the linked resource type and ID fields in the export.

Custom fields are fully supported via API using the field UUID as the key in the request payload. Boolean, date, select, text, and number field types have different payload formats documented in the API reference. We map these field-by-field during migration scoping.

Concord CRM workflows (trigger: Company/Contact/Deal created, Deal stage changed; action: Create Activity, Send Email, Trigger Webhook) are evaluated at runtime and explicitly do not execute during data import. We cannot migrate workflows. We document all active workflows during scoping for manual rebuild in the destination CRM.

Users and roles export is not available via the standard export feature. We can retrieve user data via API for email, name, and role assignment. Role permissions must be manually documented or reconstructed in the destination system.

Concord CRM does not include a document attachment export feature in the standard export tool. Attachments stored in the application must be exported manually via file system access (storage/app directory), which requires SSH or FTP access to the self-hosted server.

Pipeline stages are stored as deal properties and export as stage names or IDs. Multiple pipelines are supported but export does not include pipeline metadata. We map stage names between source and destination to maintain deal progression logic.