Migrate from Fortifi to Pipedrive

Fortifi Customers map to both Pipedrive Person (name, email, phone, address) and an Organization created from the company field. The Customer's company attribute drives the Organization creation; the Person record links to that Organization. We use email as the deduplication key for Persons. Customers without a company attribute create only a Person record. This resolves Pipedrive's requirement that Deals link to a Person or Organization.

Fortifi does not expose a native Deal or Opportunity object in its public object model, which is centered on Customers and Actions. If Fortifi Deals or custom pipeline records exist in a customer's instance, they map directly to Pipedrive Deals. Pipeline stages map to Pipedrive pipeline stages and activities. Any Fortifi deal data that is stored in Custom Properties rather than a dedicated deal object requires discovery during scoping to identify and map correctly.

Fortifi Actions are behavioral event records tracking customer interactions. Pipedrive has no native equivalent for behavioral event logs. We preserve Action type, timestamp, and metadata as Note records attached to the corresponding Person, linked at migration time through the email lookup. The customer receives a written inventory of Action types for review post-migration.

Fortifi Interactions map to Pipedrive Activities with TaskSubtype classified by channel: email Interaction maps to Activity type email; support ticket Interaction maps to type task; call Interaction maps to type call. Each Activity links to the corresponding Person or Organization record via the Person ID resolved from the email match. Timestamp, channel, and content migrate as Activity fields.

Fortifi Email records (sent, delivered, opened, bounced states with template associations) map to Pipedrive Activity records of type email. Status metadata from Fortifi (delivered, opened, bounced) migrates to custom fields on the Activity because Pipedrive Activity records do not natively track email engagement states. Campaign attribution data from Fortifi migrates as tags on the Person record.

Fortifi Conversions represent goal completions tied to marketing or sales workflows. We map Conversion records to Pipedrive Deals with a custom field conversion_type__c carrying the original Fortifi Conversion type, and conversion_date__c carrying the timestamp. Attribution data migrates to deal notes. The Deal is linked to the associated Person and Organization.

Fortifi Invoice records carry line items, payment status, due dates, and tax codes. Pipedrive has no native invoice object. We map Invoice data to Note records attached to the associated Deal, and create Pipedrive Products for line items with associated pricing. Invoice status (paid, overdue, draft) migrates to a custom picklist field on the Note. Customers requiring full invoice history visibility in Pipedrive receive a written migration of the invoice data as a structured CSV alongside the Pipedrive import.

Fortifi Subscription records define recurring billing models, cycles, and plan assignments. Pipedrive Products carry name, unit price, and currency. We create a Pipedrive Product for each unique Fortifi subscription plan, and map subscription cycle (monthly, annual) and status to custom fields on the related Deal. Advanced billing rules such as proration or usage-based tiers require manual review and are documented in the handoff inventory.

Fortifi User records (name, email, role) map to Pipedrive Users resolved by email match. Active status migrates; inactive Fortifi users become inactive Pipedrive Users. Role names from Fortifi map to Pipedrive permission sets during scoping. Any Fortifi user without a matching Pipedrive User goes to a reconciliation queue for the customer admin to provision before record import resumes.

Fortifi custom fields on Customers and other objects map to Pipedrive custom fields of matching type: text to text, number to number, date to date, dropdown to single-select picklist, multi-checkbox to multi-select picklist. We discover the complete custom property schema during scoping and create the destination custom fields in Pipedrive before migration. Custom fields without a clear Pipedrive equivalent are flagged in the handoff document with a recommended resolution.

Fortifi Automation rules, dunning sequences, and renewal triggers are configuration-level settings, not exportable data records. We do not migrate them. We deliver a written inventory of every active Fortifi automation with its trigger conditions, actions, and a recommended Pipedrive Automation rule equivalent. The customer admin rebuilds these in Pipedrive's Automation section post-migration.