Migrate from Fortifi to Salesforce Sales Cloud

Fortifi Customers are the primary contact object and may include both company-level and individual contact data. We split at migration time: company-level attributes (business name, industry, address) map to Salesforce Account, and individual contact attributes (name, email, phone, role) map to Salesforce Contact with the AccountId lookup resolved. We use the customer domain as the Account dedupe key. The original Fortifi customer record is preserved with its ID in a custom field fortifi_customer_id__c for audit.

Fortifi Actions track behavioral events against customers. Each action type becomes a Salesforce Task record with TaskSubtype set to Custom, and the action classification (e.g., login, feature_use, renewal_flagged) stored in a custom picklist field action_type__c. For high-volume action histories, we use the Salesforce Bulk API 2.0 with chunking. We preserve the original action timestamp as ActivityDate for timeline ordering.

Fortifi Conversions represent goal completions tied to marketing or sales workflows. We map conversion records to Salesforce Task records with a custom conversion_type__c field and link to the related Account or Contact via WhatId and WhoId. If the customer has Salesforce Campaign records representing the same funnel steps, we create Campaign Member entries as an alternative mapping target per the customer's scoping preference.

Fortifi Email records include sent, delivered, opened, and bounced states. We migrate to Salesforce EmailMessage records (the email content and metadata) linked to a corresponding Task record (the activity timeline entry). Email status (opened, bounced) preserves in a custom email_status__c field. Template associations migrate as a custom field template_name__c on the EmailMessage.

Fortifi Interactions track customer touchpoints across support and engagement channels. We map Interaction records to Salesforce Task for asynchronous interactions (tickets, support requests) and Event for synchronous interactions (calls, meetings). The channel type (phone, chat, email, in-person) maps to a custom interaction_channel__c picklist field. Timestamp preserves for activity timeline ordering.

Fortifi Invoices carry full financial data including line items, payment status, due dates, and tax codes. We map historical invoices to Salesforce Opportunity records (with IsClosed and IsWon set based on payment status) with OpportunityLineItem records representing the line items. This preserves revenue history for reporting without requiring the Salesforce Billing module. Invoice number maps to OpportunityName, and total invoice amount maps to Amount.

Fortifi Subscription records define recurring billing models, cycles, and plan assignments. Since Salesforce Billing is not in scope for most migrations, we map active Subscription records to Opportunity records with a custom subscription_type__c field and the billing cycle stored as a custom field. Linked invoices (already mapped above) reference back to the parent Opportunity. Advanced billing rules (proration, trial periods, seat-based pricing) require manual review and are flagged in the delivered inventory.

Fortifi supports custom fields on Customers and potentially other objects. We discover custom property schemas during scoping and map them to Salesforce custom fields using appropriate field types (text, number, date, picklist, checkbox). Custom fields receive the __c suffix per Salesforce naming convention. Fields without a clear Salesforce equivalent (e.g., Fortifi-specific enumerations) are flagged in the delivered mapping document with recommended equivalents.

If Fortifi exposes pipeline or stage management, we map pipeline definitions to Salesforce Record Types on Opportunity, each with its own Sales Process that scopes stage values. Stage probability percentages round to the nearest Salesforce-allowed integer. Pipeline-level automation triggers (if any exist) are documented for rebuild in Salesforce Flow.

Fortifi User records include role and permission assignments. We extract active users by email match against the destination Salesforce org's User table. Owners without a matching User go to a reconciliation queue. The customer's Salesforce admin provisions any missing Users before record import resumes. Role names preserve in a custom field fortifi_role__c for reference during post-migration validation.

Automation rules, dunning sequences, and renewal triggers are configuration-level settings in Fortifi. We do not migrate these as code. We document every active workflow with its trigger conditions, actions, and dependencies, and deliver a written inventory with recommended Salesforce Flow equivalents. The customer's admin or a Salesforce partner rebuilds them post-migration.

Fortifi reports and dashboards reference live data connections that do not survive export. We migrate the underlying data so equivalent reports can be rebuilt in Salesforce Reports & Dashboards. The report definitions themselves are not portable. We deliver a report mapping document listing each Fortifi report with its equivalent Salesforce report type and suggested folder structure.