Migrate from Fortifi to Freshsales

Fortifi Customers are the primary contact object and map to Freshsales Contacts (for person records) or Accounts (for organization records). We assess the customer_type or company association field in Fortifi to determine the split. Records with a named company association migrate as Contacts attached to an Account; standalone records migrate as Contacts. The original Fortifi customer ID is preserved in a custom field fortifi_customer_id__c for audit and cross-reference.

If Fortifi exposes a company or organization field linked to Customers, we map it to Freshsales Account. The domain or website from Fortifi becomes the Account Website field. Account is created before Contact import so the AccountId lookup is satisfied at insert time. Records without a company association are migrated as Contacts without a parent Account.

Fortifi Actions are behavioral event logs tracking customer interactions. We map Action records to Freshsales Task records with the action type stored in Task Subject, the original timestamp preserved in ActivityDate, and any action metadata stored in a custom field action_type__c. TaskSubtype is set based on the action classification (Call, Email, Meeting, or generic Task for other action types).

Fortifi Conversions represent marketing or sales goal completions. We map Conversion records to Freshsales Task records with conversion details in the Description field, the original conversion timestamp in ActivityDate, and the conversion source stored in a custom field conversion_source__c. If the customer uses Freshsales Pro or Enterprise and has configured a Conversion custom object, we map to that instead and create the schema during migration.

Fortifi Email records include sent, delivered, opened, and bounced states. We map to Freshsales EmailMessage records (the email content) linked to a Task record (the activity timeline entry). Email status from Fortifi maps to Freshsales EmailMessage status fields. The WhoId on Task points to the resolved Contact; WhatId points to the related Account or Deal if applicable.

Fortifi Interactions track customer touchpoints across support and engagement channels. We map Interaction records to Freshsales Task (for asynchronous interactions like support tickets) or Event (for synchronous interactions like phone calls or meetings) depending on the interaction channel type field in Fortifi. Channel type, timestamp, and duration transfer to the corresponding Freshsales fields.

Fortifi Invoice records carry full financial data including line items, payment status, due dates, and tax codes. We map Invoice records to a Freshsales custom object named Invoice because Freshsales does not include native billing. Invoice records are created with custom fields for amount, status, due_date, tax_code, and customer_link. The custom object schema is provisioned in Freshsales before invoice import. Note that Freshsales does not process payments; the customer's billing process requires a third-party integration post-migration.

Fortifi Subscription records define recurring billing models, cycles, and plan assignments. We map Subscription definitions to a Freshsales custom object named Subscription with custom fields for plan_name, billing_cycle, start_date, renewal_date, and status. Linked invoices are associated via a lookup field to the Invoice custom object. Advanced billing rules (prorated charges, trial periods, tiered pricing) are documented in the handoff notes for manual review because Freshsales custom objects do not natively execute billing logic.

Fortifi custom fields on Customers and other objects are discovered during scoping. We map each custom property to a corresponding Freshsales custom field of matching type (text to text, numeric to numeric, date to date). For picklist or multi-select fields, we verify that the value set in Fortifi matches the allowed values in the Freshsales field; mismatches are flagged for the customer's admin to resolve before migration. Custom property schema is deployed to Freshsales via the UI or API before data import.

Fortifi User records (with role and permission assignments) map to Freshsales User records. We resolve by email match. Any Fortifi User without a matching Freshsales User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Role names from Fortifi are preserved in a custom field fortifi_role__c on the Freshsales User for reference.