Migrate your Force24 data

Contacts are Force24's primary record type and export cleanly via API. We migrate all standard fields (name, email, phone, address) plus system-level properties like lifecycle stage and source. Custom Contact properties are mapped as custom fields in the destination.

Force24 associates contacts with companies, but the company record is lightweight — often just a name and URL. We preserve the association by mapping it to an Account/Company object in the destination and linking the migrated contacts.

Force24 is a marketing automation platform and does not maintain a Deals or Opportunities object. Pipeline and stage data lives in the integrated CRM, not in Force24 itself. We do not migrate deals from Force24.

Force24 stores lead records as Contacts with a lifecycle stage property indicating where a person is in the funnel. We migrate Leads as Contacts and preserve their Lifecycle Stage as a custom property in the destination.

Force24 tracks email opens, clicks, SMS replies, and form submissions against contacts. These engagement events are stored per contact and can be mapped to the destination's activity or engagement log, though schema differences require field-level mapping.

Force24 supports user-defined Custom Objects (e.g. Bookings) linked to contacts, but this feature requires an account manager to activate. We export Custom Object definitions and records, then re-link them to the migrated contact IDs. Any custom fields defined within the object are preserved.

Journeys are Force24's workflow engine — they define multi-step automation logic. Journey definitions are not stored in a portable format; we document the journey tree and trigger conditions, then recommend re-building them at the destination using the destination's automation tool.

Smart Lists are saved audience segments built from contact property filters and behavioural rules. We export the segment criteria and the contact IDs included in each segment. At the destination, we recreate the segment using equivalent filter logic.

Contacts can be tagged in Force24 for grouping and filtering. We export all contact tags and write them as Tags or Labels on the destination Contact record, preserving the full tag set.

Email templates and dynamic content blocks are Force24 assets. We export them as HTML where possible, but since they reference Force24-specific merge fields, we recommend reviewing and adapting templates in the destination's email builder after migration.

Force24 forms capture lead data and feed it into contacts and journeys. We export form field configurations and submissions, then map the submissions to the destination's contact records. The form embed code itself is destination-specific.

Lead scoring rules in Force24 assign numeric scores to contacts based on behaviour and properties. We export the score values stored on each contact. The scoring rules themselves are platform-configured and require re-implementation at the destination.

Force24 distinguishes between Marketing users and Sales users, each with different seat pricing. We map user accounts to owner or assignee fields in the destination, preserving the marketing-vs-sales role distinction where the destination supports it.

Force24 supports SMS and WhatsApp as channel options alongside email. Message history and delivery records are associated with contacts. We export these records as engagement activities against the contact, though the message content may need formatting adjustments.