Migrate from FranConnect to Salesforce Sales Cloud

FranConnect Leads map directly to Salesforce Lead. We preserve the original lead source, territory assignment (stored in a custom territory_lookup__c field), status, owner assignment, and drip campaign membership flags. Custom lead properties from FranConnect become custom Lead fields. Any active FranConnect drip campaign membership migrates as a read-only custom field listing the campaign name and current step; the customer's admin rebuilds the automation logic in Salesforce Flow post-migration.

FranConnect Contacts (franchisor staff and franchisee representatives) map to Salesforce Contact. Standard fields (name, email, phone, address) migrate cleanly. For franchisee representatives, we link Contact to the corresponding Account created from the Franchisee record. Custom contact properties map to custom Contact fields. Primary franchisee contact is flagged via a custom primary_contact__c boolean field.

FranConnect Franchisee records (individuals or entities operating units) map to Salesforce Account. FranConnect stores agreement terms, territories, and ownership stakes on the Franchisee record; these become custom Account fields (franchise_agreement_start__c, franchise_agreement_end__c, royalty_rate__c, ownership_structure__c). The Franchisee name becomes Account Name. If the Franchisee is an individual, we set Account Type to Person Account.

FranConnect Units represent operational franchise locations. We map Units to the Account's ShippingAddress fields for straightforward cases. For franchisors requiring separate location records (common in multi-unit brands), we create a custom Location__c object with a lookup to Account, storing unit-specific fields: unit_status__c, opening_date__c, site_manager__c (lookup to Contact), and custom site-level fields. The mapping approach is determined during discovery based on how the customer uses unit-level reporting.

FranConnect Territories define geographic boundaries tied to franchise agreements. We migrate territory records as a custom Territory__c object or as custom fields on Account depending on the customer's reporting model. Geographic data (coordinates, polygon definitions, exclusivity flags) migrates to custom fields. If FranConnect stores territory as shape/polygon data, we preserve it as a text blob in a custom field for admin reconstruction in a mapping tool; Salesforce does not natively render polygon boundaries. Exclusivity flags and territory status migrate as boolean and picklist fields.

FranConnect Royalty Manager stores financial ledger entries tied to units and franchisee agreements. We create a custom Royalty_Record__c object with lookup to Account (the franchisee) and Location__c (if using a separate location object). Fields include: royalty_period__c, gross_revenue__c, royalty_rate__c, royalty_amount__c, invoice_date__c, payment_status__c, payment_date__c. This is a historical financial record migration; we do not migrate active billing or payment processing logic.

FranConnect Tasks and checklists track opening procedures, compliance workflows, and operational SOPs. Task groups, dependencies, mandatory/optional flags, and reminder schedules migrate as Salesforce Task records. Parent-child task dependencies do not have a native Salesforce equivalent; we migrate as separate Task records with a custom parent_task__c lookup and document the dependency chain for the customer's admin to rebuild in Salesforce Flow if automation is required. Completed status, due dates, and assignment migrate.

Site Visit records track inspections, audits, and compliance visits at franchise units. We migrate visit summaries, completion statuses, scoring data, and response analysis as a custom Site_Visit__c object with lookup to Account (the unit). Fields include visit_date__c, visit_type__c (picklist), status__c, score__c, findings__c (long text area), and inspector__c (lookup to User or Contact). Audit charts and visualizations are rendered platform artifacts; underlying data migrates as structured records.

FranConnect's Training module tracks learning completion, certifications, and course progress for franchisee employees. We create a custom Training_Record__c object with lookup to Contact (the employee) and Location__c (the unit). Fields include course_name__c, completion_date__c, expiration_date__c, certification_status__c, and score__c. LMS-specific metadata (quiz scores, module completion percentages) migrates to custom fields. We do not migrate course content or training materials; these remain in FranConnect's document store for separate extraction.

FranConnect Support module Trouble Tickets tied to franchisee users migrate to Salesforce Case if the destination org includes Service Cloud or if the customer licenses Service Cloud at $25/user additional. Ticket status, department assignments, conversations, and resolution notes migrate. Custom ticket fields map to custom Case fields. If Service Cloud is not licensed, we map to a custom Ticket__c object with equivalent fields.

FranConnect drip campaign membership and sequence step statuses migrate as read-only custom fields on Lead and Contact: campaign_name__c, campaign_step__c, enrollment_date__c, last_action_date__c, campaign_status__c. These preserve the historical record of campaign participation but do not preserve active automation logic. We deliver a written campaign inventory with trigger conditions, step logic, and recommended Salesforce Flow equivalent for the customer's admin to rebuild post-migration.

FranConnect stores documents linked to Leads, Units, Franchisees, and Tasks. We extract document metadata (name, type, linked entity, upload date) and map to Salesforce ContentDocument with ContentDocumentLink records connecting to the appropriate parent (Lead, Account, Contact). Binary file transfers are handled separately via FranConnect's document export; we provide a document mapping inventory with URLs for manual re-upload or scripted transfer. We do not migrate document versions as binary within the standard migration scope.

FranConnect Owners (franchisor staff assigned to Leads, Units, Franchisees) map to Salesforce User records by email match. Any FranConnect Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive FranConnect owners map to inactive Salesforce Users.