CRM migration
Field-level mapping, validation, and rollback between FranConnect and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
FranConnect
Source
Nutshell
Destination
Compatibility
5 of 9
objects map 1:1 between FranConnect and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from FranConnect to Nutshell is a deliberate downselection from a franchise-lifecycle platform to a standard SMB sales CRM. FranConnect organizes data around multi-location franchise operations: Units (locations), Franchisees (operators), Territories (geographic boundaries), Royalty Manager (financial ledger), and Training records. Nutshell has none of these as native objects. We migrate what maps cleanly (People, Accounts, Leads, Deals, Activities), flag what requires manual reconstruction (Units as Account notes, Territories as custom fields, Royalty as a structured CSV export), and deliver a written inventory of drip campaigns and checklists requiring rebuild in Nutshell or a separate automation tool. FranConnect's 12-hour OAuth token expiry and per-tenant rate limit of 73,000 requests per hour govern our extraction cadence; we pre-refresh tokens and paginate to stay within ceiling. Custom fields on Leads and Contacts migrate individually with type validation against Nutshell's supported field types (text, long text, currency, date, dropdown). Workflows, sequences, and automated checklists do not migrate as code.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a FranConnect object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
FranConnect
Contacts (Franchise Development and Operate modules)
Nutshell
People
1:1FranConnect Contacts map directly to Nutshell People. Standard contact fields (name, email, phone, address) migrate cleanly. Custom contact properties are mapped individually with type validation against Nutshell's supported field types: text (225 char max for short text), long text, currency, date, and dropdown. We extract all custom contact fields during discovery and flag any that exceed Nutshell's type constraints for manual remediation before import.
FranConnect
Leads (Franchise Development)
Nutshell
Leads
1:1FranConnect Leads represent prospective franchisees entering the development pipeline and map to Nutshell Leads. We migrate Lead status, source categories, owner assignments, and associated drip campaign membership as a lead property. Active drip campaign logic does not migrate; we record the campaign name and membership date as a custom lead field for manual rebuild in Nutshell Power-Ups or a separate email cadence tool.
FranConnect
Units (Locations/Sites)
Nutshell
Accounts (with structured notes)
lossyFranConnect Units represent operational franchise locations with address, status, owner assignment, and custom site-level fields. Nutshell has no native Unit or Location object. We migrate Unit records as Nutshell Accounts with a custom field unit_status__c and structured Account notes capturing the original Unit ID, ownership type, and any franchise-specific metadata. Multi-unit hierarchies are represented as separate Accounts linked by a custom parent_account__c field where supported.
FranConnect
Franchisees
Nutshell
People + Accounts
1:manyFranConnect Franchisees (individuals or entities operating units) store agreements, territories, and ownership stakes. We split this into a Nutshell Person record (for the individual contact) and an Account record (for the franchise entity), with a custom field franchisee_id__c linking them. Territory and agreement data migrate as structured notes or custom fields on the Account. We do not migrate Franchise Agreement PDFs as binary files; we record the agreement reference and key terms in a structured format.
FranConnect
Territories
Nutshell
Custom Fields on Accounts or Leads
lossyFranConnect Territories define geographic boundaries tied to franchise agreements with coordinate or polygon data. Nutshell has no native territory object. We migrate territory names and associated metadata as a custom dropdown or text field on the relevant Account or Lead. Geographic boundary data (polygons, coordinates) migrates as a structured text blob if present; we flag this as requiring manual verification in Nutshell post-import.
FranConnect
Engagements: Calls, Emails, Meetings, Tasks, Notes
Nutshell
Activities (Calls, Emails, Meetings, Tasks, Notes)
1:1FranConnect engagement records (calls, emails, meetings, tasks, notes) from the CRM modules map to Nutshell Activities. We preserve the original timestamp for activity timeline ordering, link each activity to the correct Person or Account via the migrated record IDs, and migrate disposition, duration, and outcome data as custom activity fields where Nutshell supports them.
FranConnect
Royalty Manager Records
Nutshell
Structured CSV Export + Account Notes
1:1FranConnect Royalty Manager stores financial ledger entries (invoices, payments, royalty calculations) tied to Units and Franchisee agreements. Nutshell has no financial or accounting module. We extract the royalty ledger as a structured CSV export with Unit reference, franchisee reference, invoice date, payment amount, and royalty rate, and attach this as a named note on the corresponding Nutshell Account. The customer's finance team reconciles this CSV against their accounting system post-migration.
FranConnect
Training Records
Nutshell
Notes on Person Records
lossyFranConnect Training module tracks learning completion, certifications, and course progress for franchisee employees. Nutshell has no native LMS or training record object. We migrate training enrollment and completion status as structured notes on the relevant Nutshell Person record, listing course name, completion date, and certification status. Quiz scores and LMS-specific metadata are recorded as a note text block for manual verification.
FranConnect
Documents (linked to Leads, Units, Franchisees, Tasks)
Nutshell
Attachments on Accounts/People/Leads
1:1FranConnect stores documents linked to Leads, Units, Franchisees, and Tasks. We extract document metadata (name, type, date, linked entity) and migrate the document URL if the FranConnect document storage is accessible via API. File binaries are not migrated in the standard scope; we provide a document mapping table listing every document, its source location in FranConnect, and the target entity in Nutshell for manual file transfer or a separate document migration tool.
| FranConnect | Nutshell | Compatibility | |
|---|---|---|---|
| Contacts (Franchise Development and Operate modules) | People1:1 | Fully supported | |
| Leads (Franchise Development) | Leads1:1 | Mapping required | |
| Units (Locations/Sites) | Accounts (with structured notes)lossy | Mapping required | |
| Franchisees | People + Accounts1:many | Mapping required | |
| Territories | Custom Fields on Accounts or Leadslossy | Mapping required | |
| Engagements: Calls, Emails, Meetings, Tasks, Notes | Activities (Calls, Emails, Meetings, Tasks, Notes)1:1 | Fully supported | |
| Royalty Manager Records | Structured CSV Export + Account Notes1:1 | Mapping required | |
| Training Records | Notes on Person Recordslossy | Mapping required | |
| Documents (linked to Leads, Units, Franchisees, Tasks) | Attachments on Accounts/People/Leads1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
FranConnect gotchas
API access token expires in 12 hours with 30-day refresh window
Rate limit of 73,000 requests per hour per tenant and user
CSV import enforces strict date and character formatting
Not all modules have documented REST API endpoints
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and custom field audit
We audit the source FranConnect tenant across modules in use (Franchise Development, Operate, Royalty Manager, Training), record counts for Leads, Contacts, Units, Franchisees, Territories, Training records, and engagement volume. We audit all custom field types on Leads and Contacts and cross-reference them against Nutshell's supported custom field types. We identify which FranConnect modules have documented REST API access and which require CSV-based export via the UI. The discovery output is a written migration scope document with a full field-by-field mapping table and a list of franchise-specific objects requiring the no-equivalent treatment.
Nutshell environment setup and custom field provisioning
We provision custom fields in Nutshell for every FranConnect custom field that maps cleanly (text, currency, date, dropdown). We create custom fields for franchise-specific metadata that will appear on Accounts and People (unit_status__c, territory_name__c, franchisee_id__c, royalty_reference__c). We do not pre-create Nutshell fields for unsupported FranConnect field types; these are documented as dropped fields. Nutshell Power-Ups for basic task automation are noted as the rebuild target for FranConnect checklists.
Extraction with token management and rate limit handling
We extract data from FranConnect using the REST API for modules with documented endpoints (Leads, Contacts, Activities). For modules without API access, we use CSV export via the FranConnect UI. We implement 12-hour token expiry handling with proactive refresh to prevent mid-extraction authentication failure. We paginate requests to stay within the 73,000 requests per hour ceiling and track cumulative usage across tenant and user rate limits. Royalty Manager financial records are extracted as a structured CSV with schema aligned to the target Account note format.
Data transformation and franchise object restructuring
We transform FranConnect data into Nutshell-compatible format: Contacts to People, Leads to Leads, Units to Accounts with structured notes, Franchisees to Person+Account splits, Territories to custom fields, Training to Person notes, Royalty to structured Account notes. Engagement records are normalized to Nutshell Activity format with original timestamps preserved. We apply custom field type validation and flag any records with unsupported field values for remediation before import.
Sandbox migration and reconciliation
We run a full migration into a Nutshell trial or sandbox environment using production-like data volume. The customer's operations lead reconciles record counts, spot-checks 25-50 records against the FranConnect source, and reviews the franchise-specific flattening (Unit-to-Account notes, Territory custom fields, Royalty CSV) to confirm the representation meets business requirements. Any mapping corrections are made before production migration begins.
Production migration and cutover
We freeze FranConnect writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the complete data migration report including record counts by object, drop list of unsupported fields, and the franchise object restructuring log. We deliver a written inventory of FranConnect drip campaigns, checklists, and automated workflows requiring rebuild in Nutshell Power-Ups or a separate automation tool. We do not rebuild automations as code in the standard migration scope.
Platform deep dives
FranConnect
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across FranConnect and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
FranConnect: Not publicly documented.
Data volume sensitivity
FranConnect exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during FranConnect to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your FranConnect to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave FranConnect
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.