Migrate from Fortifi to Nutshell

Fortifi Customers map to Nutshell People with email, phone, and address fields preserved. When a Fortifi Customer has an associated company name, we also create a Nutshell Company record and link it via the Person-Company relationship. We use the company name field from Fortifi as the dedupe key during Company creation and preserve the original Fortifi Customer ID in a custom field for audit traceability.

Fortifi Actions are behavioral event logs against customers (page views, form submissions, feature usage). We map action type classifications and timestamps to Nutshell Activities with the action type stored as activity details and the original timestamp preserved. If the customer uses Fortifi's action log for sales engagement history, these migrate as Activity records on the linked Person.

Fortifi Conversions represent goal completions tied to marketing or sales workflows. We map conversion records with their attribution data to Nutshell Deals, creating pipeline stages in Nutshell that correspond to the customer's Fortifi conversion funnel stages. Conversion value migrates to Deal value and attribution source data becomes a custom field on the Deal.

Fortifi email records (sent, delivered, opened, bounced states with template associations) migrate as Nutshell Activities linked to the Person record. We preserve email status flags in activity details and migrate campaign attribution data as custom fields on the Activity record. If the customer uses Nutshell's Engagement suite post-migration, these activities inform campaign segmentation.

Fortifi Interactions track customer touchpoints across support and engagement channels. We preserve the interaction log, channel type, and timestamp as Nutshell Activity records. Channel type (email, phone, chat, in-person) migrates as activity details. If Fortifi Interactions reference a specific support or service context, we flag those for the customer to review in Nutshell's task management context.

Fortifi Invoice records carry full financial data including line items, payment status, due dates, and tax codes. Nutshell has no native billing engine, so we migrate Invoice data as structured custom field data attached to the Person or Company record. Payment history and outstanding balances become custom fields. Customers who rely on invoice data for reporting should consider integrating Nutshell with a dedicated billing tool (Stripe, Quadient, or similar) post-migration.

Fortifi Subscription records define recurring billing models, cycles, and plan assignments linked to customers and invoices. We migrate subscription definitions and linked invoice data as custom field data on the Person or Company in Nutshell. Active or cancelled status, billing cycle, and plan name become custom fields. Advanced billing rules (proration, trial periods, usage-based billing) require manual review and cannot be automatically represented in Nutshell's CRM data model.

Fortifi supports custom fields on Customers and potentially other objects. We discover the custom property schema during scoping and map each to a Nutshell custom field of the closest equivalent type. Multi-value properties map to Nutshell custom fields where supported. Any custom properties without a clear Nutshell equivalent are flagged as custom field data that requires manual categorization post-migration.

Fortifi User records with role and permission assignments map to Nutshell Users. We resolve by email match and preserve role names as a reference. Active users migrate as active Nutshell Users. If the customer uses Nutshell's free onboarding support, the admin assigns Nutshell permission levels post-migration based on the Fortifi role documentation we provide.