Migrate from Force24 to HighLevel

Force24 Contacts map directly to GoHighLevel Contacts. All standard fields (first name, last name, email, phone, address) transfer as typed fields. The Force24 lifecycle stage property (subscriber, lead, marketing qualified, sales qualified, customer) migrates as a custom text property lifecycle_stage__c on the GoHighLevel Contact so the original funnel position is preserved. Any Force24 custom contact properties (beyond the standard set) migrate as custom fields using GoHighLevel's custom fields API. Deduplication runs on email address during import to prevent duplicate Contact creation.

Force24 associates contacts with Company records (typically lightweight: name and URL). GoHighLevel Contact has a company_name field rather than a formal Company object by default. We map the Force24 company name to the GoHighLevel Contact company_name field and preserve the company domain URL in a custom field company_website__c. If GoHighLevel's Company module is active in the destination account, we create Company records and link them via the contact relationship instead.

Force24 tags on contacts migrate as GoHighLevel Labels on the Contact record. We export the full tag set per contact and write each tag as a GoHighLevel Label. Tags used for audience segmentation in Force24 Smart Lists carry over as static Labels, which GoHighLevel uses for filtering in its pipeline and workflow triggers. The customer chooses at scoping whether tags become Labels or remain as custom field values.

Force24 Smart Lists save complex filter combinations (property-based and behavioural AND/OR conditions) that update in real time. We export the contact IDs belonging to each Smart List and recreate the membership as static GoHighLevel Contact Groups or Tags. The dynamic filter logic itself cannot transfer. We document each Smart List's criteria in the migration handoff document so the customer's admin can rebuild active segments using GoHighLevel's filter builder.

Force24 tracks email opens, clicks, SMS replies, WhatsApp messages, and form submissions as engagement events against contacts. We export engagement records with timestamp, channel, and interaction type and import them as GoHighLevel Notes with a custom tag or activity log entry on each Contact. Email engagement metrics (opens, clicks) are stored as custom numeric fields on the Note. This preserves the interaction history for sales rep review without a native engagement timeline in GoHighLevel.

Force24's lead scoring engine assigns a numeric score to contacts based on behavioural and property rules. The score value stored on each contact migrates as a custom numeric field lead_score__c on the GoHighLevel Contact. The scoring rules themselves (property weights, threshold conditions) are Force24 platform configuration and do not transfer. We document the rule structure for the customer's admin to rebuild using GoHighLevel workflow logic or a third-party scoring integration.

Force24 Custom Objects (e.g. Bookings, Event Registrations) store linked-data records against contacts. We export Custom Object definitions and records, then create equivalent GoHighLevel Custom Objects using GoHighLevel's Custom Object API. Each record is re-linked to the target GoHighLevel Contact via a Contact lookup field. Force24 Custom Objects require account manager activation and non-standard API access; we coordinate with Force24 support before export. If the destination GoHighLevel account does not have Custom Objects enabled, we store the data as JSON in a custom long-text field on the Contact record as a fallback.

Force24 Automated Journeys define multi-step, multi-channel workflows with conditional branching, wait steps, and behavioural triggers. Journey logic is stored in Force24's workflow engine and is not exported as a portable format. We document each active journey's structure: entry trigger, step sequence, branch conditions, exit criteria, and estimated daily volume. The customer rebuilds journeys in GoHighLevel's Workflow builder using the documentation as a specification. We do not convert journey logic automatically.

Force24 forms capture lead data and feed it into contacts and journeys. We export form field configurations (field names, types, required flags) and form submissions as contact property updates. The form embed code and styling are Force24-specific. We import form submissions as Contact records with submission timestamp and source form name in a custom field form_source__c. The form builder interface and embedded form copies require re-build in GoHighLevel's form editor.

Force24 distinguishes between Marketing users (per-seat priced) and Sales users (unlimited). We extract all active Force24 user accounts and map them to GoHighLevel Users by matching email address. Any Force24 user without a matching GoHighLevel account is held in a reconciliation queue for the customer's admin to provision before contact import. Owner assignments on contacts transfer as GoHighLevel OwnerId once the User mapping is resolved.