Migrate from Snapforce CRM to HubSpot

SnapForce Accounts map directly to HubSpot Companies. Company name, domain/website, industry, employee count, and annual revenue transfer as HubSpot Company properties. Parent-account hierarchies in SnapForce map to HubSpot's associated companies model — the primary company link resolves first, secondary associations are recorded as a custom property for reference.

SnapForce Contacts map directly to HubSpot Contacts — name fields, email, phone, job title, address, and create/update timestamps transfer as HubSpot Contact properties. The original SnapForce create date is preserved as a custom datetime field because HubSpot's built-in create date reflects the migration timestamp.

SnapForce's separate Lead module merges into HubSpot Contacts. All SnapForce Lead records become HubSpot Contacts with lifecycle_stage set based on the SnapForce Lead status — open leads receive 'lead', qualified leads receive 'MQL', and converted leads receive 'customer'. The original Lead status value is preserved in a custom property for HubSpot admin reference.

SnapForce Deals map to HubSpot Deals — deal name, amount, expected close date, owner, and pipeline stage transfer as HubSpot Deal properties. HubSpot's Deal object requires a Pipeline to be selected; FlitStack maps each SnapForce pipeline to a corresponding HubSpot pipeline before the migration runs.

SnapForce pipelines with custom stage names map to HubSpot pipelines. Each pipeline stage name in SnapForce becomes a HubSpot Deal stage value. Stage order and probability are mapped per pipeline so the deal funnel reflects the source pipeline layout. Custom pipeline settings such as visibility and automation triggers are documented for manual recreation in HubSpot.

SnapForce call logs transfer as HubSpot engagements with type 'call'. Subject, duration, notes, owner, and timestamp map to HubSpot's engagement call properties. Call recordings attached in SnapForce are exported as files and re-uploaded to HubSpot's file manager, linked to the associated Contact or Deal record.

SnapForce email logs map to HubSpot email engagements. Subject, body, recipient, sender, and timestamp transfer. Original timestamps are preserved as engagement timestamps in HubSpot. Attachments from SnapForce email records are re-hosted as HubSpot file attachments. Inline images and embedded links are preserved as references, and large attachments are flagged for chunked upload if they exceed HubSpot's 25 MB limit.

SnapForce meeting records map to HubSpot meeting engagements — title, start time, end time, location, attendees, and body text transfer. Owner and associated Contact/Deal links are preserved in HubSpot's engagement associations. Recurring meeting series are identified by a unique pattern ID and may require manual recreation of the series in HubSpot's calendar integration if recurrence data is present.

SnapForce notes map to HubSpot notes. Note body, create date, last modified date, and owner transfer. Rich-text formatting in SnapForce notes is preserved where possible; plain-text fallback is applied if the source formatting exceeds HubSpot's note field compatibility. Additionally, any embedded images are exported as file attachments and linked to the note record for reference.

SnapForce file attachments on Accounts, Contacts, Leads, and Deals are exported and re-uploaded to HubSpot's file manager, then linked back to the corresponding HubSpot record (Company, Contact, or Deal). File size limits for HubSpot uploads apply; files exceeding 25 MB are flagged for chunked upload or alternative hosting.

SnapForce custom fields on Accounts, Contacts, Leads, and Deals map to HubSpot custom properties on the corresponding object. Field types (text, number, pick-list, date, checkbox) are translated to HubSpot's equivalent field types. Pick-list custom fields require value-by-value mapping where the SnapForce pick-list values differ from HubSpot's default options.

SnapForce users are matched to HubSpot users by email address. Unmatched users are flagged before migration — teams either invite the user to HubSpot first or assign records to a designated fallback owner. The SnapForce user ID is preserved in a custom property on migrated records for audit traceability.

SnapForce workflow definitions are exported as a JSON reference document for manual rebuild in HubSpot Workflows. SnapForce workflows covering lead assignment, follow-up triggers, and field-update rules cannot be auto-converted because HubSpot Workflows operate on a different trigger-and-action model. The export document is delivered as part of the migration package.

SnapForce custom reports and dashboards with SQL-standard filters and chart widgets do not migrate. The underlying data (contacts, deals, activities) moves to HubSpot, but report layouts must be rebuilt in HubSpot's reporting interface. FlitStack delivers a list of source report names and their key metrics as a rebuild checklist.