Migrate from FranConnect to Microsoft Dynamics 365 Sales

FranConnect Leads map directly to Dynamics 365 Lead. We extract status, source categories, owner assignments, and drip campaign membership flags as custom fields on the Lead record. The franchise development pipeline stages (Prospect, Qualified, Agreement Sent, Agreement Signed) map to Dynamics 365 Lead Status values. Drip campaign membership migrates as a text property or multi-select picklist rather than an active automation.

FranConnect Contacts (franchisor staff and franchisee representatives) map directly to Dynamics 365 Contact. Standard contact fields (name, email, phone, address) migrate cleanly. Custom contact properties are mapped to equivalent Dynamics 365 custom fields on Contact. Owner assignment migrates by resolving the FranConnect owner email to a Dynamics 365 User record.

FranConnect Units represent operational franchise locations. We map Units to Dynamics 365 Account records where the franchisee is a business entity, with the unit manager as a related Contact record linked to that Account. Unit status, address, and site-level custom fields migrate as Account fields or related custom entities. Multi-unit hierarchies may require flattening if the franchise model uses nested unit structures not supported by the flat Account model.

FranConnect Franchisee records (individual or entity operators) map to Dynamics 365 Account. We preserve the franchisee-agreement relationship, territory assignment, and ownership stakes as custom fields on the Account record. Royalty-related properties migrate as configuration fields or to a linked Royalty custom object if the franchise-specific schema is being replicated.

FranConnect Territories define geographic boundaries with coordinate or polygon data tied to franchise agreements. Microsoft Dynamics 365 Sales has no native Territory object at the sales rep assignment level beyond the standard Territory Management module (Enterprise tier). We create a Territory__c custom object with geography fields, associate units via lookup, and flag exclusivity status. The customer chooses whether to use Dynamics 365's built-in Territory Management or the custom object approach during scoping.

FranConnect Royalty Manager stores financial ledger entries (invoices, payments, royalty calculations) tied to Units and Franchisee agreements. Microsoft Dynamics 365 Sales has no native royalty tracking. We create a Royalty__c custom object with invoice number, payment date, amount, status, and lookup links to the Account (Franchisee) and Account (Unit). The customer's finance team reviews the mapping to confirm that historical royalty data is suitable for migration versus archival in a separate database.

FranConnect Site Visit records track inspections, audits, and compliance visits at Units. We map visit summaries, completion status, scoring data, and response analysis to a SiteVisit__c custom object linked to the Unit Account. Visit tasks and reminders migrate as Task records assigned to the appropriate User. Audit charts and visualization data do not migrate as rendered artifacts; underlying data migrates as structured records.

FranConnect Support module Trouble Tickets migrate to Dynamics 365 Case if Service Cloud is licensed. Ticket status, department assignments, conversation history, and resolution notes map to Case fields and EmailMessage records. Custom ticket properties map to Case custom fields. If Service Cloud is not included in the destination license, tickets migrate to a SupportTicket__c custom object as a fallback.

FranConnect stores documents linked to Leads, Units, Franchisees, and Tasks. We extract document metadata and URLs where accessible. File binaries migrate to a SharePoint document library provisioned for the Dynamics 365 environment, with ContentDocumentLink records created to attach files to the appropriate Account, Contact, or Lead. Document folder structure maps to SharePoint library folders reflecting the franchise hierarchy.