Migrate from Fortifi to Twenty CRM

Fortifi Customers split into Twenty's Company record (company-level fields: name, domain, address) and a primary Contact record (personal fields: name, email, phone, job title). The split is based on whether the Fortifi Customer record contains person-level or organization-level data. We preserve the original Customer ID in a custom field for cross-reference during reconciliation.

Fortifi Subscription records define recurring billing models, plan assignments, and cycle data. These map to a Twenty custom object created via the /metadata API before migration. Fields include plan name, billing cycle, start date, status, and a lookup to the parent Company. Advanced billing rules (proration, trial extensions) are flagged for manual review post-migration.

Fortifi Invoice records carry full financial data: line items, payment status, due dates, tax codes, and totals. We migrate these to a Twenty custom Invoice object with a lookup to the parent Company and Subscription. Invoice PDFs are stored as attachments linked via ContentDocumentLink. Payment history is preserved as a related custom object or as fields on the Invoice record.

Fortifi Actions are behavioral event logs against Customers (page views, form submissions, feature usage). We map these to Twenty Task records with type classification preserved in the Subject or a custom field, and a link to the parent Company or Contact via WhatId or the primary relationship field.

Fortifi Conversions represent marketing or sales goal completions tied to workflows. We map Conversion records to Twenty Opportunity, preserving attribution data (source, campaign, channel) in Opportunity fields and a link to the primary Company. If Fortifi tracks a monetary value on the Conversion, that becomes the Opportunity Amount.

Fortifi Email records include sent, delivered, opened, and bounced states with template associations. We migrate the email body and metadata as a Twenty Task (activity timeline entry) linked to the parent Company or Contact. Template associations and engagement states are preserved in custom Task fields for reporting.

Fortifi Interactions track customer touchpoints across support and engagement channels. We map Interaction records to Twenty Task with channel type (phone, chat, email, in-person) preserved in the Subject or a custom field, timestamp preserved as ActivityDate, and body or notes migrated as the Task description.

Fortifi User records include role and permission assignments. We extract active Users by email match against Twenty WorkspaceMembers. Role names migrate as custom fields on the WorkspaceMember record. Permission set details are documented for manual verification post-migration.

Fortifi supports custom fields on Customers and potentially other objects. We discover the custom property schema during scoping, pre-create equivalent custom fields in Twenty via the /metadata API before data migration, and map values field-by-field. Any Fortifi custom property without a clear Twenty equivalent is flagged with a data type recommendation.

Fortifi automation rules, dunning sequences, and renewal triggers are configuration-level settings stored in the platform and not exportable as data records. We document the full automation configuration during discovery including trigger conditions, action sequences, and timing rules, and deliver this as a written handoff document for the customer's admin to rebuild in Twenty. This is not in standard migration scope.