Migrate from Force24 to HubSpot

Force24 contacts map 1:1 to HubSpot contacts. HubSpot's contact model uses a flat property list — Force24 contact fields migrate as HubSpot contact properties. Primary company association maps to HubSpot's primary company link; additional company associations surface as secondary company links.

Force24 companies map directly to HubSpot companies, including standard fields such as name, domain, phone, industry, and number of employees. Parent‑child hierarchies in Force24 translate to HubSpot's parent company field, with the top‑most company becoming the root. When a Force24 contact links to multiple companies, we keep the primary association as HubSpot's primary company and add secondary links for the relationships; duplicate company names are flagged for review.

Force24 journeys and campaign automation rules have no native HubSpot equivalent. FlitStack exports the complete journey configuration — triggers, conditions, and action steps — as a structured JSON reference document. Your HubSpot admin uses this to rebuild the logic in HubSpot workflows.

Force24 calculates lead scores using behavioral and demographic scoring rules. HubSpot has no native lead-score field. We preserve the current Force24 score value as a custom number property (Lead_Score__c) on each HubSpot contact — the score at migration time is preserved for reporting continuity.

Force24 automated smart lists and segmentation rules define dynamic contact groups. HubSpot lists serve a similar function but operate differently. FlitStack exports the filter logic (field conditions, operators, and values) so your team can recreate the segments as HubSpot static or active lists.

Force24 tracks email opens, clicks, and send history linked to contacts. HubSpot stores these as engagement timeline entries. We migrate the engagement record summary as a HubSpot note with the engagement type, timestamp, and outcome (opened/clicked/bounced) so the activity history is visible on the contact timeline.

Force24 custom objects (Enterprise tier) storing entities like bookings or product references map 1:1 to HubSpot custom objects. The custom object fields migrate as HubSpot custom properties. N:1 links to contacts map as HubSpot custom object associations; N:N links require a HubSpot junction custom object.

Force24 tags label contacts with descriptive values like industry segment or source campaign. HubSpot has no native tag field. We map tags to a HubSpot multi-select custom property (Contact_Tags__c) or split each significant tag into its own boolean custom property — your admin chooses the structure during planning.

Force24 owner IDs link to the user or team responsible for a contact or deal. HubSpot owners are HubSpot user records. We resolve Force24 owner IDs by email match against the HubSpot user list. Unresolved owners are flagged before migration so your team can either invite them to HubSpot or reassign their records to a fallback owner.

Force24 captures form submissions as contact records with source and submission metadata. HubSpot stores form submissions as contact properties and engagement events. We migrate the form identifier and submission timestamp as HubSpot contact properties, and include the submission details as a note on the contact.

Force24 records lifecycle or engagement stage as a contact property. HubSpot's lifecycle_stage property exists natively but may not match Force24's stage labels. If Force24 uses a custom stage model, we map it to a HubSpot custom pick-list property (Lifecycle_Stage_Source__c) to preserve the original values.

Force24 tracks marketing contact status (opted-in, consented, etc.) as a contact property. HubSpot's marketing contact flag is a billing and compliance distinction separate from CRM properties. We preserve the Force24 marketing flag as a boolean custom property (Marketing_Contact_Flag__c) for reference and compliance records.