Migrate from FranConnect to Pipedrive

FranConnect Leads represent prospective franchisees in the development pipeline with status, source categories, and owner assignments. We migrate these to Pipedrive People and route them through the Leads Inbox or import directly as Persons depending on the customer's sales process stage. Original franchise development source and territory interest are preserved as custom fields on the Person record since Pipedrive does not have a native franchise lead type.

FranConnect Contacts (franchisor staff and franchisee representatives) migrate to Pipedrive People. Standard fields (name, email, phone, address) map directly. Custom contact properties migrate as custom fields on the Person object. FranConnect contact type flags (Franchisor Staff vs. Franchisee Contact) are preserved in a custom Person field for segmentation.

FranConnect Units represent operational franchise locations with address, status, owner assignment, and site-level custom fields. We map Units to Pipedrive Organizations, using the unit's operating name as the Organization name and the franchisee's contact as the primary Person linked to that Organization. Unit status (Active, Development, Closed) migrates as a custom Organization field.

FranConnect Franchisee records store the individual or entity operating one or more units with associated agreements, territories, and ownership stakes. Corporate franchisees (entities) map to Pipedrive Organization; individual franchisees map to Person linked to the corresponding Unit Organization. We use the Franchisee type field to determine the split at migration time and preserve original franchise agreement dates and territory exclusivity flags as custom fields on the destination record.

FranConnect Territories define geographic boundaries tied to franchise agreements with exclusivity flags and associated units. Pipedrive has no native territory or geographic boundary object. We migrate territory data as custom fields on the Organization (territory_name__c, territory_exclusivity__c, territory_type__c) and as a custom multi-select picklist if the franchise operates multiple territories per franchisee. Geographic polygon or coordinate data migrates as text fields with a note to the customer to evaluate a mapping integration post-migration.

FranConnect Tasks and operational checklists (opening procedures, compliance workflows, SOPs) migrate to Pipedrive Activities. Task groups, mandatory/optional flags, and reminder schedules map to custom Activity fields. We do not replicate checklist UI in Pipedrive; we convert each checklist item to an individual Activity with the parent checklist name stored in the Activity subject or a custom field. Task dependencies and completion order are preserved in the Activity description.

FranConnect Site Visit records track inspections, audits, and compliance visits at franchise units. We migrate visit summaries, completion status, visit date, and visit type as a Pipedrive Activity linked to the corresponding Unit Organization. Scoring data and response analysis migrate as custom Activity fields. Audit charts and radar chart visualizations are not transferable; we preserve the numeric scores and link to the source report URL if available.

FranConnect drip campaigns linked to Leads and Contacts are marketing automation features that do not have a direct Pipedrive equivalent. We migrate campaign membership and sequence step statuses as Person custom fields (campaign_name__c, last_sequence_step__c, campaign_enrolled_date__c). Active campaign logic is not replicated in Pipedrive; we document the campaign structure for the customer's admin to rebuild using Pipedrive Campaigns or a connected sales engagement tool.

FranConnect Support module tickets (tied to franchisee users) migrate to Pipedrive Activities attached to the corresponding Person or Organization. Ticket status, department assignment, and resolution notes migrate as custom Activity fields. Pipedrive does not have a native Case or Ticket object; we use the Activity type (call, task, or meeting) with custom fields to preserve ticket metadata. High-volume support-to-ticket migration requires customer scoping to determine if a dedicated ticketing integration is needed post-migration.

FranConnect documents linked to Leads, Units, Franchisees, and Tasks store metadata (filename, URL, linked record) that we migrate as Pipedrive Notes with a reference link to the original FranConnect document URL. File binaries do not transfer through the migration pipeline; FranConnect's document management requires a separate file export via FranConnect's UI, which the customer coordinates outside the migration scope.

FranConnect Royalty Manager stores financial records including invoices, payments, and royalty calculations tied to units and franchisee agreements. Pipedrive does not have a financial ledger, invoice management, or royalty tracking module. We do not migrate Royalty Manager records. We deliver a written record of the Royalty Manager schema (table names, field list, record count) so the customer's finance team can evaluate a dedicated franchise financial management system or ERP integration post-migration.

FranConnect's BI module generates franchise performance dashboards, KPI visualizations, and development pipeline analytics. These are platform-rendered artifacts that do not export as raw data. We migrate the underlying data (Lead status counts, unit opening metrics, site visit scores) as Pipedrive custom fields and Organization-level metrics so the customer's Pipedrive admin can build equivalent reports. BI dashboard reconstruction requires a separate reporting scope post-migration.