Migrate from Fortifi to HighLevel

Fortifi Customers map directly to GoHighLevel Contacts. The Fortifi customer name, email, phone, company, and address fields map to GoHighLevel Contact standard fields. We use the Fortifi customer email as the dedupe key during import to prevent duplicate Contacts. Any Fortifi customer-level tags or segments map to GoHighLevel Contact Tags or a custom multi-select field on Contact. Fortifi tier customer count caps (2,500 / 20,000 / unlimited) have no GoHighLevel equivalent because GoHighLevel includes unlimited Contacts on every paid plan.

Fortifi Actions are behavioral event logs tied to Customers tracking things like page visits, form submissions, and custom events. GoHighLevel does not have a native equivalent event-log object, so we map Actions to GoHighLevel Activities with a descriptive body field, or to a custom field on Contact (action_type__c + action_timestamp__c) for high-value event types. If the customer has fewer than 50 distinct action types, we create a Contact custom field for each; for larger catalogs, we store the action log as an Activity note or as a JSON-serialized custom field. This is a configuration decision made during scoping.

Fortifi Conversion records represent goal completions tied to marketing or sales workflows and carry attribution data. These map to GoHighLevel Opportunities with the conversion name as the Opportunity name, conversion date as the created date, and attribution source stored in custom Opportunity fields. If Fortifi exposes a monetary conversion value, it maps to the Opportunity amount field. The customer identifies which Fortifi Conversions represent sales pipeline entries versus marketing goal completions during scoping.

Fortifi Invoice records carry full financial data including line items, payment status, due dates, and tax codes linked to Customers. GoHighLevel does not have a native invoice accounting object, so we map Invoices to GoHighLevel Opportunities with invoice metadata in custom fields (invoice_number__c, invoice_status__c, due_date__c, amount_paid__c, tax_amount__c), or to a custom Invoice object if the customer requires line-item detail preservation. We preserve the Customer-to-Invoice link by ensuring the Contact is created before any Invoice-related Opportunity import.

Fortifi Subscription records define recurring billing models, cycles, and plan assignments linked to Customers and Invoices. GoHighLevel Opportunity objects do not natively capture subscription metadata, so we store subscription fields (plan_name__c, billing_cycle__c, next_renewal_date__c, subscription_status__c) as custom fields on the related Contact or Opportunity, or as a custom Subscription object if the customer requires full subscription lifecycle tracking. Advanced billing rules (proration, trial-to-paid transitions, usage-based billing) require manual review and may be rebuilt in GoHighLevel Workflows post-migration.

Fortifi Email records include sent, delivered, opened, and bounced states with template associations and campaign attribution. We map email history to GoHighLevel Contact Activities with a note capturing subject, status, and timestamp. Campaign attribution data migrates to custom fields on Contact (last_campaign__c, email_open_count__c). Note: GoHighLevel email deliverability runs on shared Mailgun infrastructure, and reviewers consistently report lower inbox placement rates than dedicated email platforms. We flag this in the gotchas and recommend warming a dedicated sending domain with proper SPF/DKIM/DMARC configuration post-migration.

Fortifi Interactions track customer touchpoints across support and engagement channels with channel type and timestamp. We map Interaction records to GoHighLevel Activities on the Contact timeline, with the channel type stored in an activity note or custom field (interaction_channel__c). Historical interaction volume is preserved, though the GoHighLevel Activity object does not natively support the same interaction taxonomy as Fortifi; we create custom Activity types during schema setup to match the customer's interaction classification.

Fortifi Custom Properties on Customers and other objects are discovered during scoping and mapped to GoHighLevel Custom Fields on the equivalent object (Contact, Company, Opportunity). We use GoHighLevel's Custom Field editor to pre-create fields before import. Any Fortifi custom property without a clear GoHighLevel equivalent is flagged in the mapping document with a recommended approach (custom field, tag, or note field). Fortifi's limited public schema documentation means custom property discovery relies on per-customer review of the live Fortifi configuration.