Migrate from CRUMP CRM to HubSpot

CRUMP contacts map directly to HubSpot contacts via email-based deduplication to prevent duplicate records. Owner resolution runs by matching CRUMP owner email addresses against existing HubSpot user accounts. Records without a matching email are flagged in a pre-migration report for manual owner assignment before the full migration run executes. This prevents orphaned records and ensures proper assignment chains are maintained from day one in HubSpot.

CRUMP company records map to HubSpot company records using company name and domain as matching keys for deduplication. HubSpot supports N:N contact-to-company associations, allowing multiple contacts to link to the same organization. The primary company designation is set from CRUMP's primary-company relationship field. Secondary associations are created via HubSpot's association API after contact records land in the system.

CRUMP deals map to HubSpot deals with direct field mapping for amount, closedate, and dealname columns. CRUMP's multi-pipeline setup means each CRUMP deal carries a pipeline reference that must be translated to the corresponding HubSpot pipeline ID. HubSpot deal records are created within the pipeline that matches CRUMP's original pipeline assignment, preserving deal-to-pipeline relationships throughout the migration process.

CRUMP supports multiple independent pipelines, each with custom stage configurations and probability weightings. When CRUMP contains more than one pipeline, FlitStack offers two approaches: create multiple HubSpot pipelines mirroring CRUMP's existing structure, or consolidate all CRUMP pipeline stages into a single HubSpot pipeline with merged stage sets. Your team selects the consolidation strategy during the planning phase before migration runs to align with your reporting structure.

CRUMP task records including calls, emails, and meetings logged against contacts or deals map to HubSpot engagements in the CRM. Original activity timestamps and owner assignments are preserved during the transformation to maintain accurate audit trails. HubSpot's engagement timeline displays these activities chronologically on each contact and deal record, giving teams full visibility into customer interaction history.

CRUMP notes map to HubSpot notes with rich-text formatting preserved where the source format remains compatible with HubSpot's note editor. CRUMP note attachments migrate as HubSpot file attachments linked to the same parent record, maintaining context for important customer discussions. This preserves the contextual information and attached reference materials that sales teams rely on for understanding deal history and customer interactions.

CRUMP stores owners as Dynamics User GUIDs, which are 32-character identifiers that have no meaning in HubSpot's system. FlitStack resolves each Dynamics GUID to the corresponding owner's email address by querying the Dynamics user table, then matches that email against HubSpot user accounts. Unresolved owners are surfaced in a pre-migration report for your team to map manually before data transfer begins.

CRUMP custom entities derive from Dynamics 365 custom tables. If your HubSpot account is on Enterprise tier, we create HubSpot custom objects and map the records directly. For Starter, Professional, or Team tiers, CRUMP custom entity fields migrate as custom properties on the standard Contact or Deal object — your admin chooses the target object during planning.

CRUMP files attached to Dynamics annotations (email attachments, note attachments, entity file attachments) are downloaded from the Dynamics backing store and re-uploaded to HubSpot's file manager. Files over 25 MB are flagged; your team decides whether to split or exclude them from the migration.

Each CRUMP pipeline stage name maps to a HubSpot deal stage name in the target pipeline. CRUMP stage probabilities are stored as a custom field in HubSpot since HubSpot's stage probability is tied to the stage pick-list, not a separate field. Stage-transition timestamps from CRUMP are preserved in a custom datetime field.

CRUMP bundles project management, helpdesk, and invoicing alongside CRM. These modules have no direct HubSpot equivalent. Project and helpdesk records must be exported separately and archived or rebuilt in dedicated tools. We can export these as structured CSVs for reference or re-import into HubSpot tickets (Service Hub) where applicable.

CRUMP automations run on the Dynamics layer (Power Automate flows, plugin steps, workflow definitions). These do not migrate. We export your workflow definitions as a JSON reference document for your HubSpot admin to rebuild using HubSpot workflows or Operations Hub.