Migrate from FranConnect to Twenty CRM

FranConnect Leads represent prospective franchisees entering the development pipeline. We migrate Leads with status, source categories, owner assignments, and drip campaign configurations as People records in Twenty. The franchise development pipeline stage (Prospect, Qualified, Application, Approval) maps to a custom single-select field development_stage__c on the People object. Owner assignments resolve by email against Twenty Members. Drip campaign membership status migrates as a read-only property field; active campaign logic is not rebuilt in Twenty.

FranConnect Contacts cover both franchisor staff and franchisee representatives. Standard contact fields (name, email, phone, address) migrate cleanly to Twenty People. Custom contact properties are mapped individually during discovery, with FranConnect field types mapped to their Twenty equivalents (text, number, date, select, multi-select). The contact type distinction (franchisor staff vs franchisee rep) is preserved as a custom type__c picklist field on People.

FranConnect Units represent operational franchise locations. We map unit records including address, status, owner assignment, and custom site-level fields to Twenty Company records. The unit's operational status (Active, Inactive, Coming Soon, Closed) maps to a custom status__c field. Multi-unit hierarchies (a franchisor managing regional groupings of units) are represented by creating parent Company records for regions and linking units as child Companies via a custom parent_company__c lookup field.

FranConnect Franchisees are the individuals or entities operating units. We create People records for individual franchisee contacts with a custom franchisee_id__c reference field back to the Franchisee entity. The franchise agreement details, ownership percentage, and entity type (individual vs LLC vs corporation) migrate as custom fields on the People record. Territory assignments are resolved by linking the franchisee People record to the corresponding Territory Company record.

FranConnect Territories define geographic boundaries tied to franchise agreements. We create a custom Territory object in Twenty (Settings → Data Model) with fields for geographic name, boundary coordinates or polygon data, exclusivity flags, and associated franchise agreement references. Territory records link to the parent Franchisor Company record and to all associated Unit Company records. Coordinate or polygon data migrates as a text field; mapping visualization must be rebuilt in Twenty's UI post-migration.

FranConnect Tasks and checklists cover opening procedures, compliance workflows, and operational SOPs. Task groups, dependencies, mandatory/optional flags, and reminder schedules migrate as Twenty Task records with custom fields capturing checklist item status. Checklist dependencies are represented as linked Task records with a custom dependency_type__c field. We do not replicate active reminder triggers; the customer recreates these in Twenty after migration.

FranConnect Site Visit records track inspections, audits, and compliance visits at units. We create a custom Site_Visit object in Twenty or represent visits as Task records with a custom type__c = Site_Visit value. Visit summaries, completion statuses, scoring data, and response analysis migrate with the linked Company (Unit) reference. Audit charts and rendered visualizations cannot migrate as data; we document the chart configuration for manual rebuild.

FranConnect Royalty Mgr stores financial ledger entries including invoices, payments, and royalty calculations tied to units and franchisee agreements. We create a custom Royalty_Record object in Twenty with fields for invoice number, amount, payment date, royalty rate, period, associated franchisee (People), and associated unit (Company). Historical ledger entries migrate as read-only records; active billing workflows require rebuild in Twenty.

FranConnect Training tracks learning completion, certifications, and course progress for franchisee employees. We create a custom Training_Record object in Twenty with fields for course name, completion date, certification status, associated franchisee employee (People), and associated unit (Company). LMS-specific metadata such as quiz scores and time-in-module migrates where available; video or interactive content does not transfer.

FranConnect Support module stores Trouble Tickets tied to franchisee users. We map tickets to Twenty Case records with status, department assignment, description, and resolution notes. Custom ticket field mapping is done during discovery. Case resolution dates and SLA status migrate as custom fields. Active ticket workflows and escalation rules do not migrate and require rebuild in Twenty Cases.