Migrate from Crank CRM to HubSpot

Direct 1:1 map. HubSpot's Contact object receives all standard Crank CRM contact properties. The primary company association maps to a HubSpot contact-to-company association via HubSpot's associations API. Any secondary company associations on the same contact are added as additional associations on the same HubSpot record.

Crank CRM's flexible property model means any custom fields on contacts — region codes, lead sources, product interests — become HubSpot custom contact properties. These are created before migration and typed to match (string, number, date, picklist). Picklist values require value-by-value mapping if the options differ from HubSpot defaults.

Direct 1:1 map. HubSpot's Company object receives all standard company properties from Crank CRM. Parent-company hierarchies in Crank CRM map directly to HubSpot's parent company lookup field. Multi-company contacts are preserved as additional HubSpot associations on the primary company record, with secondary associations retained for full relationship context.

Any custom fields on Crank CRM company records — sector tags, account tiers, renewal dates — become HubSpot custom company properties. These are created before migration with correct data types to ensure type consistency. Multi-select picklists in Crank CRM map to HubSpot multi-checkbox properties, preserving all selected values.

Direct 1:1 map. Crank CRM deal records map to HubSpot deals. The deal's primary contact association links via HubSpot's deal-to-contact association. Additional contacts on the deal use additional association records. Deal stage values require value-mapping against HubSpot pipeline stage names.

Crank CRM deal stage values (e.g., Prospecting, Qualification, Proposal, Closed Won, Closed Lost) map to corresponding HubSpot pipeline stage names. If Crank uses custom stage names, we create a HubSpot pipeline matching those names and map values 1:1. Stage probabilities are applied per HubSpot pipeline configuration.

Custom fields on deals — deal type, probability override, custom priority flags, renewal terms, or internal identifiers — become HubSpot custom deal properties. Non-standard picklist values require value-mapping against HubSpot's allowed values for the property type before migration begins.

Crank CRM activity records migrate as HubSpot engagements. Calls become engagement calls, emails become engagement emails, meetings become engagement meetings. Each preserves the original timestamp, owner, and body/note content. Custom metadata on the activity (e.g., call duration, email open count in Crank) migrates as custom engagement properties.

Crank CRM notes migrate as HubSpot engagement notes with full rich-text formatting preserved. Notes are linked to their parent record — contact, company, or deal — via HubSpot's association model. The original create date and owner are retained as engagement metadata for complete audit trails.

If your Crank CRM plan includes custom objects, they map 1:1 to HubSpot custom objects on the Enterprise tier. On Starter or Professional, custom objects are migrated as sets of custom properties on the nearest standard object — typically Contact or Company — with a linking custom ID property for reference.

Crank CRM contact-to-company associations with non-default labels (e.g., 'Partner', 'Vendor') migrate as additional HubSpot contact-to-company associations. The association type is set to contact_to_company. Label values that don't match HubSpot's built-in types are stored in a custom contact property for reference.

C rank CRM owner records resolve to HubSpot users by email match. Any Crank owner without a corresponding HubSpot user is flagged before migration. Their records are assigned to a designated fallback HubSpot owner so no record lands without an owner at migration time.