Migrate from FranConnect to Freshsales

FranConnect Leads from the Sky Develop module map directly to Freshsales Lead records. We preserve Lead Status, Lead Source Category and Detail, Owner assignment, and any custom lead properties. Drip campaign membership status migrates as a custom Lead field (e.g., campaign_membership_status__c) rather than as active campaign logic; the campaign sequence itself does not transfer. Email is used as the dedupe key during import.

FranConnect Contact records (franchisor staff and franchisee representatives) map to Freshsales Contacts with standard fields (Name, Email, Phone, Address) migrated directly. Custom contact properties are individually mapped to Freshsales custom fields. We resolve Contact-to-Lead deduplication by email to prevent duplicate records in the destination.

FranConnect Unit records map to Freshsales Account records because Accounts natively support address, site/location type, and owner assignment. Unit-specific fields (unit status, opening date, lifecycle stage, reference dates for milestone tracking) are mapped to custom Account fields. Multi-unit hierarchies with parent-unit relationships are flattened into a top-level Account hierarchy using Freshsales' Account hierarchy feature.

FranConnect Franchisee records (individual or entity operating a unit) require a split. The entity-level data (company name, ownership structure, agreement details) maps to a Freshsales Account. The individual contact data (primary representative, email, phone) maps to a Contact linked to that Account via a lookup. Territory and exclusivity flags are stored as custom fields on the Account. This split requires up-front value mapping for any franchisee type codes used in FranConnect.

FranConnect Territory records define geographic boundaries tied to franchise agreements. We map territory name, exclusivity flag, and associated unit count to a custom Territory custom object or to custom fields on the linked Account. Polygon or coordinate data is stored as a text field (WKT or GeoJSON string) where Freshsales' standard address fields do not capture geographic precision. The customer decides on the territory representation approach during scoping.

FranConnect Tasks and operational checklists (used for unit opening procedures, compliance SOPs, and site audit checklists) migrate to Freshsales Task records. Task Group names, mandatory/optional flags, and reminder schedules migrate as custom Task fields. Dependencies between tasks are documented but not recreated as automation in Freshsales since Freshsales Workflows cannot natively model multi-step task dependencies without custom development. Checklist item completion status migrates as a custom Task field.

Site Visit records (inspections, audits, compliance visits) map to Freshsales Tasks with a custom Task record type (Site Visit) where visit type, scoring data, and response analysis are stored as custom fields. If the visit records carry structured inspection data with multiple line items, we evaluate a custom Site_Visit__c object with child Inspection_Item__c records. Audit charts and rendered visualizations do not migrate as files; the underlying visit data migrates as structured records.

FranConnect Royalty Manager stores invoices, payments, and royalty calculations tied to Units and Franchisee agreements. We extract the financial ledger entries and map them to a custom Royalty_Record__c object with fields for invoice_id, payment_date, amount, unit_id (lookup to Account), and franchisee_id (lookup to Account or Contact). Royalty calculation logic does not migrate because it is franchise-specific; the customer configures any calculation rules in Freshsales custom fields or a connected ERP.

Training module records (learning completion, certifications, course progress) migrate to a custom Training_Record__c object linked to the Contact or Account representing the franchisee employee. Quiz scores and LMS-specific metadata are stored as custom fields. Course hierarchy and curriculum logic do not migrate; these are rebuilt in Freshsales as custom fields or as a separate LMS if required.

FranConnect documents linked to Leads, Units, Franchisees, and Tasks are migrated as Freshsales Notes with the document URL stored in the Note body or a custom URL field. File binary transfers are not handled as part of the standard migration scope; we recommend FranConnect's document storage remain accessible for a transition period or that the customer configure a linked document management system post-migration.