Migrate from FranConnect to HighLevel

FranConnect Leads represent prospective franchisees entering the development pipeline with status, source categories, owner assignments, and territory interest. We map these to GoHighLevel Contacts with a custom text field franchise_lead_status__c carrying the original FranConnect status value, and a custom picklist franchise_source_category__c for the source attribution. Owner assignments resolve via email match to GoHighLevel Users.

Standard FranConnect Contact records (franchisor staff and franchisee representatives) migrate directly to GoHighLevel Contacts with name, email, phone, and address fields. Custom contact properties migrate to GoHighLevel custom fields pre-created during schema design. Any lookup relationships to FranConnect Units and Franchisees resolve to GoHighLevel Contact custom fields holding the external franchise record ID.

FranConnect Units represent operational franchise locations with address, status, owner assignment, and custom site-level fields. GoHighLevel has no native location/unit object, so we create a Franchise_Unit__c custom object with fields for address, unit_status__c, franchisee_id__c (lookup), and any custom site-level properties from FranConnect. The custom object is created before Contact migration so that lookups resolve at insert time.

FranConnect Franchisee records (individuals or entities operating units) store agreements, territories, and ownership stakes. We map these to a Franchisee__c custom object with fields for entity_name__c, agreement_type__c, ownership_stake__c, and territory_ids__c (multi-select or text list of associated territory external IDs). Units operated by each franchisee link via a lookup relationship Franchisee__c on Franchise_Unit__c.

FranConnect Territory records define geographic boundaries tied to franchise agreements with polygon or coordinate data. GoHighLevel has no native territory object. We create a Territory__c custom object with fields for territory_name__c, geographic_definition__c (text or long-text for coordinate data), exclusivity_flag__c, and franchisee_id__c (lookup). Polygon and coordinate data that cannot be stored as standard text fields are flagged for admin-side review and potential integration with a mapping tool post-migration.

FranConnect Tasks and checklists (used for opening procedures, compliance workflows, and operational SOPs) migrate to GoHighLevel Tasks with task groups preserved as custom fields, mandatory_optional__c flag, and reminder schedule data in description or custom date fields. We do not rebuild checklist dependencies or conditional logic; these are documented in the workflow handoff inventory for the admin to re-implement in GoHighLevel's workflow builder.

Site Visit records track inspections, audits, and compliance visits at FranConnect Units. We create a Site_Visit__c custom object linked to Franchise_Unit__c with fields for visit_date__c, completion_status__c, scoring_data__c (numeric or text), and response_analysis__c. Audit charts and rendered visualizations do not migrate; the underlying visit data and scores transfer as structured fields.

Royalty Manager stores financial records including invoices, payments, and royalty calculations tied to units and franchisee agreements. We create a Royalty_Record__c custom object linked to Franchise_Unit__c and Franchisee__c with fields for invoice_number__c, payment_date__c, royalty_amount__c, and invoice_status__c. The financial ledger migrates as structured custom fields; recurring payment automation requires rebuild in GoHighLevel's workflow builder or a third-party accounting integration.

Training module tracks learning completion, certifications, and course progress for franchisee employees. We migrate enrollment records and completion status to a Training_Record__c custom object linked to Contact (employee) with fields for course_name__c, completion_date__c, certification_status__c, and score__c (if numeric). LMS-specific metadata such as quiz scores and instructor notes map to custom fields where feasible or document as notes for admin review.

FranConnect stores documents linked to Leads, Units, Franchisees, and Tasks. We extract document metadata and URLs where accessible and migrate as GoHighLevel Notes attached to the relevant Contact or custom object record. File binary transfers are handled separately via FranConnect's document export wizard; the destination storage approach (GoHighLevel native file storage or linked external URLs) is decided during scoping based on the customer's plan tier and storage limits.

The FranConnect Support module stores Trouble Tickets tied to franchisee users. We create a Support_Ticket__c custom object linked to Contact with fields for ticket_number__c, status__c, department__c, conversation_log__c (long text), and resolution_notes__c. Custom ticket field mappings are resolved during schema design. Active ticket workflows require rebuild in GoHighLevel's automation engine.