Migrate from Force24 to Nutshell

Force24 Contacts map to Nutshell People records, with Contacts that have a lifecycle_stage indicating pre-qualified status (subscriber, lead, marketing qualified lead) migrated as Nutshell Leads, and those with sales qualified or customer lifecycle stages migrated as Nutshell Contacts. The original Force24 Lifecycle Stage is preserved as a custom field on the Nutshell record for audit. The split rule is defined during scoping based on the customer's specific lifecycle stage configuration.

Force24 Company associations (a lightweight name and URL record linked to Contacts) map to Nutshell Accounts. We use the Force24 company name as the Account name and the domain as the Website field. The Account record is created before Contact import so that the Account lookup is satisfied at the moment of Contact insert.

Force24 tracks email engagement events (opens, clicks), SMS delivery records, and form submissions against contacts. We migrate these as Nutshell Activities of type Email or Note. The original Force24 engagement timestamp becomes the Activity date, preserving the chronological timeline. Activity notes carry the engagement type and summary (e.g., 'Email opened: subject line') so the sales rep sees the history in context.

Force24 contact tags are exported in full and mapped to Nutshell in one of two ways depending on volume and plan: small tag sets become a Nutshell custom multi-select text field; large tag sets become Nutshell Groups with People assigned. The customer selects the strategy during scoping. Tag names are preserved verbatim.

Force24 Smart Lists define complex filter combinations against contacts. We export the contact IDs that are members of each Smart List and recreate them as static Nutshell Lists (or Groups). The saved filter query itself cannot be transferred. We document the filter criteria for each Smart List so the customer's admin can recreate the dynamic logic manually in Nutshell.

Force24 Custom Objects store linked-data records (bookings, event registrations) associated with contacts. Nutshell does not have a native Custom Object equivalent at its standard tiers. We export Custom Object records and evaluate whether they can be represented as additional custom fields on the Nutshell People record. If the Custom Object schema exceeds what custom fields can reasonably hold, we flag it for manual re-entry post-migration. This decision is made during scoping and documented in the migration scope.

Force24 Automated Journeys define multi-step, multi-channel workflows with conditional branching, wait steps, and behavioural triggers. Journey logic is not stored in a portable format and cannot be migrated as automation code. We audit each active Journey, document its trigger, steps, branches, and exit conditions in a written specification, and deliver it to the customer for manual rebuild in Nutshell or a third-party automation tool.

Force24 assigns numeric lead scores to contacts based on engagement rules. We export the score value stored on each contact record and write it to a Nutshell custom number field (e.g., original_lead_score). The scoring rules themselves are platform-configured and do not migrate. We document the rule structure for the customer's admin to evaluate recreating as a Nutshell workflow or integration logic.

Force24 distinguishes between Marketing and Sales user seats. We map user accounts by email match to Nutshell Owners. Any Force24 Owner without a matching Nutshell user goes to a reconciliation queue for the customer's admin to provision before the People migration begins.

Force24 email templates and dynamic content blocks are exported as HTML. Because they reference Force24-specific merge fields, we do not recommend direct import into Nutshell's email builder without review. We provide the HTML files and a recommendation to copy content into Nutshell's email editor manually, which ensures merge fields are updated to Nutshell's format.