Migrate from Fortifi to HubSpot

Fortifi's unified customer record decomposes into HubSpot's Contact (the primary person) and Company (the organization they belong to). The customer's billing address and company-level fields map to the Company record; personal contact fields map to the Contact record. We preserve the Fortifi customer ID on both HubSpot records for traceability.

Individual contacts associated with a Fortifi customer map 1:1 to HubSpot Contacts. Name, email, phone, job title, and address fields transfer directly. Owner resolution happens by email match against HubSpot users; unmatched owners are flagged for manual assignment before the migration loads.

Organization-level data from a Fortifi customer (company name, domain, industry, employee count, address) maps to a HubSpot Company record. HubSpot Company properties like domain, industry pick-list, and number of employees receive direct values where Fortifi fields align; mismatched pick-list values are mapped value-by-value or stored as a custom property for manual categorization.

Fortifi invoices carry line items, amounts, payment status, and due dates. These map to a HubSpot Deal with Line Items representing each invoice line. The Deal name derives from the invoice number or customer name. Payment status and amount overdue map to custom properties since HubSpot Deals do not natively track invoice aging. Historical paid invoices map as closed-won Deals with original close dates preserved.

Fortifi subscription records (plan tier, billing cycle, renewal date, MRR) map to a HubSpot Deal with custom properties capturing the subscription tier name, monthly recurring revenue amount, billing frequency, and next renewal date. The Deal stage reflects the subscription lifecycle (active, trial, canceled). Multiple subscriptions per customer generate multiple Deal records.

Fortifi tracks interactions (actions, emails sent, form submissions) as activity records. These map to HubSpot's engagement timeline — emails as email engagements, calls as call engagements, meetings as meeting engagements, and notes as note engagements. Original timestamps and owners are preserved. We skip action types that have no HubSpot equivalent (e.g., internal system events) and log them in the audit report.

Any custom fields defined in Fortifi (beyond the standard customer, contact, invoice, subscription fields) require a corresponding custom property in HubSpot. We extract the field name, data type, and pick-list values from Fortifi's schema and deliver a custom property creation plan for HubSpot before the migration runs. Multi-select pick-list values map value-by-value; date fields map to HubSpot date properties; numeric fields map to HubSpot number properties.

Fortifi owner assignments on customers, contacts, and invoices resolve by email match to HubSpot user accounts. We generate a pre-flight owner resolution report listing matched owners, unmatched owners, and the records affected. Your team resolves unmatched owners before the migration commits. Records without a resolved owner default to a designated HubSpot fallback owner specified by your admin.

Fortifi's built-in GDPR compliance and tax configuration do not have a direct HubSpot equivalent. We export Fortifi's consent and compliance settings as a structured reference document for your HubSpot admin to rebuild using HubSpot's GDPR tools and custom properties. Consent timestamps map to a HubSpot custom property for audit reference.

Documents and files attached to Fortifi customer records, invoices, or subscriptions are downloaded and re-uploaded to HubSpot Files. Files are associated with the corresponding Contact, Company, or Deal record by their original attachment context. File size limits follow HubSpot's attachment constraints. Inline images in notes are extracted and rehosted within HubSpot's file storage.