Migrate your Fortifi data

Customers are the primary contact object in Fortifi. Every tier enforces a hard customer count cap (2,500 / 20,000 / unlimited). We migrate customer records with standard fields (name, email, company, contact details) and preserve any custom properties added to the customer profile.

Actions are the primary activity/event object tracking behavioral events against customers. We preserve the action log history and type classifications so reporting dashboards and automation triggers remain intact in the destination system.

Conversions represent goal completions tied to marketing or sales workflows. We map conversion records with their attribution data and associated customer links to preserve funnel reporting.

Email records include sent, delivered, opened, and bounced states along with template associations. We migrate email history and related campaign attribution data.

Interactions track customer touchpoints across support and engagement channels. We preserve the interaction log, channel type, and timestamp for each record.

Invoices carry full financial data including line items, payment status, due dates, and tax codes. We migrate invoice records with their associated customer and subscription linkages intact.

Subscription records define recurring billing models, cycles, and plan assignments. We map subscription definitions and their linked invoices, though advanced billing rules may require manual review post-migration.

Fortifi supports custom fields on Customers and potentially other objects. We discover custom property schemas during scoping and map them to destination equivalents, flagging any that lack a clear equivalent.

If Fortifi exposes pipeline or stage management for sales processes, we map pipeline definitions and stage associations. Documentation of pipeline-specific features is limited in public sources.

User records include role and permission assignments. We map active users and preserve role names, though permission set details may require post-migration verification.

Automation rules, dunning sequences, and renewal triggers are configuration-level settings rather than exportable data records. We document the workflow configuration for manual re-implementation in the destination system.

Pre-built and custom reports reference live data connections that do not survive export. We migrate the underlying data so reports can be rebuilt; the report definitions themselves are not portable.