Migrate from Centrium CRM to HubSpot

Centrium contacts map 1:1 to HubSpot contacts. HubSpot requires an email address for contact creation — contacts without emails migrate with a placeholder email and a custom Original_Contact_ID__c field for traceability. This ensures all contact records can be reconciled against the Centrium source even when email addresses were not originally captured in the source system.

Centrium company records map to HubSpot companies. HubSpot's company domain property (domain_name) is populated from Centrium's website field during migration. Parent-company hierarchies map to HubSpot's parent_company_id, preserving organizational structures where subsidiaries are linked to parent accounts.

Centrium N:1 contact-to-company links map to HubSpot association records. The primary company per contact is determined by Centrium's default association or most-recently-modified flag. Secondary companies are added as additional HubSpot associations, maintaining the full relationship graph from Centrium within HubSpot's association model.

Centrium deals map to HubSpot deals. Each deal's stage in Centrium maps to a HubSpot deal stage within a designated pipeline. HubSpot pipelines must be pre-created; FlitStack delivers a pipeline configuration plan based on Centrium's stage count and names. This mapping preserves deal progression history and enables accurate pipeline reporting in HubSpot.

Centrium deal stages map value-by-value to HubSpot deal stages. Stage names are matched textually where possible; non-matching stages are mapped to the closest HubSpot stage with a note for admin review. Stage-entered dates in Centrium become HubSpot deal stage history entries.

Centrium deal-to-contact links migrate to HubSpot deal-contact associations. HubSpot's default association type is used. If Centrium stores a role label (e.g., Decision Maker) on the association, it migrates as a custom deal property for reference. This preserves the context of each contact's role within the deal even though HubSpot's native association model does not include role fields.

Centrium tasks map to HubSpot tasks. Task subject, body, due date, completion status, and owner email are preserved. HubSpot tasks associate to contacts, companies, or deals — task-to-record links are mapped during migration to maintain activity context. This ensures that historical task activity appears in the correct contact and deal timelines after migration completes.

Centrium project records have no native HubSpot equivalent. On HubSpot Enterprise, projects migrate as a custom object with a name, description, status, and linked tasks. On lower tiers, projects are stored as HubSpot tasks with a Project_Name__c custom property and a custom pipeline view for grouping.

Centrium notes map to HubSpot engagements of type note. Original create timestamps are preserved. Rich-text formatting in Centrium notes is stripped to plain text for HubSpot compatibility unless the note contains HTML that maps cleanly. This ensures note readability in HubSpot while preserving the original content and creation dates for audit trail purposes.

Centrium custom fields on contacts map to HubSpot custom contact properties. Field types are matched: text→string, number→number, date→date, picklist→enumeration. Picklist values require value-by-value mapping where the source and destination picklist options differ. This type matching ensures data integrity when values transfer to HubSpot's property schema.

Centrium custom fields on deals map to HubSpot custom deal properties. All custom properties must be pre-created in HubSpot before the migration run — FlitStack delivers a HubSpot property setup plan as part of the migration package. This pre-creation step ensures the target schema is ready before data transfer begins, preventing migration failures due to missing properties.

Centrium owner IDs are resolved by email against HubSpot users. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts for them or assigns their records to a fallback owner. This prevents orphaned records and ensures all migrated deals and tasks have valid owner assignments in HubSpot from day one.