Migrate from Force24 to Zoho CRM

Force24 Contacts with a lifecycle stage of subscriber, lead, or marketing qualified lead map to Zoho CRM Lead. Force24 Contacts with lifecycle stage of sales qualified lead, opportunity, or customer map to Zoho CRM Contact tied to a Zoho CRM Account. We compute the split using Force24's lifecyclestage property at migration time and preserve the original stage in a custom field on the Zoho record for audit. This split mirrors how Zoho's CRM is designed to operate and avoids orphaned Contacts without an Account parent.

Force24 Companies (a lightweight record with name and URL) map to Zoho CRM Accounts. The Force24 company domain becomes the Account Website field and acts as a dedupe key during import. Accounts are created before Contact import so that Account lookups are satisfied at Contact insert time. Any Force24 contact without a company association becomes a Contact without an Account lookup, which is valid in Zoho CRM.

Force24 lead scoring assigns numeric values to contacts based on behaviour and property rules. We export the score value stored on each contact record and write it to a custom numeric field in Zoho CRM. The scoring rules themselves (the conditional logic that computes the score) are Force24 platform configuration and cannot be exported; we document the active scoring rules for the customer to rebuild in Zoho using Workflow Rules or a Zoho-compatible scoring tool.

Force24 contact tags migrate as either Zoho CRM Tags (a native tagging feature on Leads and Contacts) or as a custom multi-select picklist field depending on tag volume and usage pattern. We export the full tag set, assess how many unique tags exist, and recommend Tags for moderate tag counts or a custom field for high-cardinality taxonomy migrations.

Force24 Smart Lists save complex filter combinations (property-based, behavioural, AND/OR conditions) against the contact database. We export which contact IDs belong to each Smart List and recreate the membership as Zoho CRM static lists or custom lookup fields. The saved filter logic itself is not portable; we document each Smart List's criteria so the customer's admin can rebuild it using Zoho's Dynamic View or Workflow Rule filters.

Force24 tracks email open events, click events, and delivery status per contact. These engagement records migrate as Zoho CRM Activity Task records with the engagement type stored in a custom Activity Type field. Activity timestamps are preserved from the Force24 engagement record to maintain the chronological history on the Zoho Contact or Lead timeline.

Force24 SMS and WhatsApp message history (sent, delivered, replied) is associated with contacts as engagement events. We migrate these as Zoho CRM Activity Task records with Subtype = SMS, the message content preserved in the task description, and the delivery status stored in a custom field. Replies are logged as a separate inbound activity.

Force24 form submissions are engagement events on the contact record. We migrate each form submission as a Zoho CRM Activity Task with the form name stored in a custom field, submission timestamp preserved, and any submitted field values mapped to a custom field or stored in the task description for audit.

Force24 Custom Objects (linked-data tables for bookings, event registrations, and similar records) require account manager activation before they are visible to the API. We confirm activation during scoping. Each Custom Object type maps to a Zoho CRM Custom Module created in the destination org before migration. Custom Object records are exported from Force24, and lookups are re-established to the migrated Zoho Contact or Account using email or contact ID as the matching key. The Custom Module field types (text, numeric, date, lookup) are mapped to equivalent Zoho field types.

Force24 Marketing and Sales user accounts map to Zoho CRM Users. We match by email address. Any Force24 owner without a matching Zoho User record is held in a reconciliation queue for the customer's admin to provision before record import continues, since OwnerId references are required on most Zoho standard modules.

Force24 email templates and dynamic content blocks are platform assets. We export templates as HTML files. Because Force24 templates reference Force24-specific merge fields, the HTML requires review and adaptation in Zoho CRM's email template builder post-migration. We provide the exported files and a field-mapping note identifying which Force24 merge tags map to Zoho CRM merge fields.