Migrate from Crust CRM to HubSpot

Crust contacts map directly to HubSpot contacts. Email address serves as the unique identifier for matching records between systems. Owner resolution matches Crust owner email to HubSpot user email for proper assignment. Contacts without a primary company link land as standalone HubSpot contacts, and we preserve the original Crust create date as a custom property for historical reference.

Crust company records map 1:1 to HubSpot companies without transformation. The company domain field maps to HubSpot's domain property for automatic contact-company association upon import. Parent-company hierarchies in Crust map via HubSpot's parent company association, preserving organizational structure through the migration.

Crust deals map to HubSpot deals as the core revenue object. Each Crust deal stage maps to a HubSpot pipeline stage with probability values transferred as custom numeric fields if HubSpot's probability per stage doesn't match Crust's custom probability model. Deal owner assignments resolve via email matching similar to contact ownership.

Crust custom modules require HubSpot Enterprise custom objects at the destination. Each module maps as a named custom object with its Crust fields represented as custom properties. N:N module associations between modules need HubSpot junction-object equivalents, which FlitStack AI structures using association properties during migration.

Crust activity logs including notes, call logs, and meeting records map to HubSpot engagements with original timestamps preserved for audit continuity. Call activities map to HubSpot logged calls; meeting records map to HubSpot meetings with duration and attendees captured in the engagement properties.

Crust tasks map to HubSpot tasks with subject, due date, priority, and owner preserved. Completed status transfers directly to HubSpot's task completion field. Overdue logic and reminder settings are destination-side configuration that your team sets post-migration based on HubSpot's task notification settings.

Crust file attachments re-upload to HubSpot Files using the bulk file import mechanism. Files are linked to the parent record (contact, company, or deal) via HubSpot's file association model using association type IDs. File size limits per HubSpot's storage tier apply and are validated during the import pass.

Crust owner records resolve by email match against HubSpot users in the destination account. Unmatched owners are flagged and reported before migration begins. Your team either creates HubSpot user accounts for unmatched owners first or assigns those records to a designated fallback owner during the migration pass.

Crust tags applied to contacts or companies map to HubSpot properties if the tag set is finite and manageable within HubSpot's property constraints. High-cardinality tags with many unique values may need to remain as custom properties rather than HubSpot lists to avoid property enumeration limits.

Crust workflows, triggers, and automation rules do not migrate to HubSpot due to incompatible schema formats. We export the workflow definitions as a structured JSON reference document including trigger conditions, action steps, and filter logic so your HubSpot admin can rebuild them in HubSpot's workflow editor.

Any Crust contact property that doesn't match HubSpot's standard contact property schema migrates as a HubSpot custom property. Property type matching includes text, number, date, and picklist formats aligned to HubSpot's supported custom property types during migration.

Crust deal stages map value-by-value to HubSpot pipeline stages using a configured mapping table. Each Crust stage name becomes a HubSpot stage name within your target pipeline. Stage order and probability percentages are preserved as configured in Crust, transferred to HubSpot's pipeline stage settings.