Migrate from Force24 to Freshsales

Force24 Contacts map to Freshsales Contacts as the primary record. All standard fields (name, email, phone, address) migrate along with system-level properties and lifecycle stage, which we write to a custom field lifecycle_stage__c on the Freshsales Contact for audit and reporting. The contact-to-account association from Force24 (where a contact is linked to a company) maps to Freshsales Contact.account_id via the Accounts phase.

Force24 Companies map to Freshsales Accounts. The company name becomes Account Name, and the domain or website URL migrates to the Account Website field. Accounts are migrated first in dependency order so that the account_id lookup on Contact is satisfied at the moment of Contact insert. Force24's lightweight company records (often just a name and URL) expand to Freshsales Account fields; additional Force24 company properties become Freshsales custom Account fields.

Force24 links each Contact to a Company record. We resolve this relationship during migration by matching Force24 company_id to Freshsales Account.id after the Accounts phase completes. The resolved account_id is written to each Contact's account_id field in Freshsales. This is the most commonly missed lookup in CRM migrations; we validate it with a reconciliation count before closing the Contacts phase.

Force24 Lead records (contacts with a lifecycle stage indicating funnel position) migrate to Freshsales Leads. We preserve the full Force24 lifecycle stage in a custom field original_lifecycle_stage__c on the Freshsales Lead, and any Force24 lead score value migrates as an integer to freshsales_lead_score__c. Lead ownership (Force24 owner email) maps to Freshsales OwnerId via the User reconciliation phase.

Force24 tracks email opens, email clicks, SMS messages, form submissions, and web tracking events against contacts. These engagement records migrate to Freshsales Task (for calls, emails, and tasks) and Event (for meetings and appointments). Each Task receives a custom field engagement_type__c to identify the source channel. Activity dates are preserved as Task ActivityDate to maintain the timeline order that sales reps rely on. Force24's web tracking events without a specific contact association are logged as Notes against the relevant Contact record.

Force24 contact tags migrate to a Freshsales custom field (tag_list__c) using a multi-select picklist data type. The full set of distinct tags is extracted during discovery, and the picklist values are created in Freshsales before migration. Contacts with multiple tags receive all their tags as selected values in the single multi-select field, preserving the grouping and segmentation logic that Force24 tags represent.

Force24's numeric lead scoring values assigned per contact migrate to a custom integer field on both Lead and Contact in Freshsales. The Force24 scoring rules themselves (the conditional logic that assigns points) are not migrated; we deliver a written description of the scoring model so the customer's Freshsales admin can configure Freddy AI's scoring rules or a Freshsales Workflow to replicate the logic using Freshsales' native automation tools.

Force24 Custom Objects (linked-data tables for bookings, event registrations, or other domain-specific records) require account manager activation on the source side before the API is accessible. We confirm activation status during discovery and coordinate with Force24 support to obtain API access for export. In Freshsales, we pre-create the equivalent custom object schema using Freshsales' custom object or custom field tooling before any records are imported. Custom Object records are loaded last in dependency order because they often have lookup relationships to migrated Contacts, Accounts, or Leads. If the Custom Object has a simple flat structure, we use Freshsales custom fields on the Contact or Account instead of a separate object.

Force24 Smart Lists define audience segments using property filters and behavioural rules. We export the contact IDs included in each Smart List as static lists in Freshsales. The saved filter query itself is not portable; we document each Smart List's criteria (property conditions, behavioural triggers, AND/OR logic) in a written segment inventory so the customer's admin can recreate the active, real-time segments as Freshsales filters or dynamic lists post-migration.

Force24 Automated Journeys are not stored in a portable format and do not migrate as workflow logic. We document each journey's structure — entry trigger, step sequence, conditional branches, wait steps, and exit conditions — as a written specification. The customer uses this document to rebuild journeys in Freshsales Workflows. We do not transfer journey logic automatically.