Migrate from Concord CRM to HubSpot

Concord contact records map directly to HubSpot contacts. The Concord contact's associated company ID resolves to a HubSpot company VID before the contact import runs. Concord owner email matches HubSpot user email for OwnerId assignment. During import, we verify each associated company exists in HubSpot, and any missing owners are flagged for you to assign a fallback before the migration proceeds.

Concord phone, mobilephone, and phone_extension properties map directly to HubSpot phone, mobilephone, and num_employees properties. No transformation required — values copy as-is into the corresponding HubSpot contact properties. If a contact has multiple phone numbers stored in Concord, each number copies to its matching HubSpot field, and any extra numbers are appended to a custom notes field for reference.

Concord company records map to HubSpot companies with name, domain (as Website), industry (value-mapped to HubSpot's pick-list), number of employees, and annual revenue all transferring directly. Concord parent-company hierarchy uses a separate lookup. The value mapping for industry ensures that each Concord free-text entry is translated to the nearest HubSpot pick-list option, with any unmatched values defaulted to 'Other' unless a custom mapping is provided.

Concord company domain maps to HubSpot company Website. Industry values require value-by-value mapping because Concord stores free-text industry names while HubSpot uses a constrained pick-list — mismatched values default to 'Other' or a specified fallback. We generate a pre-migration report listing all distinct industry values found in Concord, allowing your team to define custom mappings before the import begins.

Concord dealname maps to HubSpot dealname. Concord amount maps to amount. closedate maps to closedate. The Concord deal stage value maps to a specific HubSpot dealstage within the destination pipeline — value mapping required per pipeline. During the mapping phase, we confirm that each target pipeline exists in HubSpot and create it if needed, ensuring stage names align with your business process.

Concord stages are simple per-instance pick-list values. HubSpot stages are pipeline-scoped. We map each Concord stage name to a named HubSpot stage within your target pipeline and preserve original stage-entered dates as custom datetime fields on the deal. If your HubSpot pipeline includes probability weights for each stage, we configure those probabilities in the mapping configuration so the deal forecast reflects expected outcomes.

Concord products map to HubSpot products with SKU, name, price, and currency. Products must exist before deal-line items reference them, so products migrate before deals in the sequence. During product migration, we validate that each SKU is unique and that pricing aligns with your currency settings, ensuring that line items in deals link correctly after the import.

Concord activity records map to HubSpot engagements with original timestamps and owner email preserved. Concord activity body maps to HubSpot engagement body. Concord calls become HubSpot call engagements; emails become email engagements; meetings become meeting engagements; notes become note engagements.

Concord custom fields on contacts map to HubSpot custom contact properties. Concord uses the custom field ID in API payloads — we translate these to HubSpot internal property names. Multi-select pick-list fields map to HubSpot text fields with comma-separated values unless hubspot_multiple_selectors is configured.

Concord custom fields on deals and companies create HubSpot custom deal and company properties. We create the property in HubSpot before the migration run if it does not exist, using the same field type (text, number, date, pick-list, checkbox) from Concord's field definition.

Concord workflows (triggers: Company/Contact/Deal Created, Deal Stage Changed, Missed Call; actions: Create Activity, Send Email, Trigger Webhook) are not exportable. We document the workflow logic — trigger events, conditions, and action sequences — as a written specification your HubSpot admin uses to rebuild in HubSpot's workflow builder.

Concord file attachments export from the server filesystem and re-upload to HubSpot Files. Files attach to the corresponding CRM record by association. Concord's public/storage symlink directory is the extraction source. We recommend performing a dry-run of the file export to verify that all files are readable and that file path references map correctly to HubSpot's file management system.