CRM migration

Migrate from FranConnect to Nutshell

Field-level mapping, validation, and rollback between FranConnect and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

FranConnect logo

FranConnect

Source

Nutshell

Destination

Nutshell logo

Compatibility

56%

5 of 9

objects map 1:1 between FranConnect and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

FranConnect logo

FranConnect

What's pushing teams away

  • Interface navigation is non-intuitive for new users — the learning curve is steep and the home button layout requires multiple clicks to reach key sections
  • Perceived complexity for smaller franchise systems — some operators find the feature breadth overwhelming relative to their actual needs
  • Reports indicate the platform can slow during peak usage hours, affecting performance visibility when it matters most
  • Switching costs are significant given the franchise-specific data model — lead pipelines, task checklists, and royalty structures are tightly coupled to FranConnect conventions
  • Enterprise pricing without a free trial creates commitment risk, particularly for emerging brands evaluating fit before full adoption

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How FranConnect objects map to Nutshell

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)

maps to

Nutshell

People

1:1
Fully supported

FranConnect 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)

maps to

Nutshell

Leads

1:1
Mapping required

FranConnect 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)

maps to

Nutshell

Accounts (with structured notes)

lossy
Mapping required

FranConnect 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

maps to

Nutshell

People + Accounts

1:many
Mapping required

FranConnect 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

maps to

Nutshell

Custom Fields on Accounts or Leads

lossy
Mapping required

FranConnect 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

maps to

Nutshell

Activities (Calls, Emails, Meetings, Tasks, Notes)

1:1
Fully supported

FranConnect 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

maps to

Nutshell

Structured CSV Export + Account Notes

1:1
Mapping required

FranConnect 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

maps to

Nutshell

Notes on Person Records

lossy
Mapping required

FranConnect 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)

maps to

Nutshell

Attachments on Accounts/People/Leads

1:1
Fully supported

FranConnect 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.

Gotchas + challenges

What specifically takes care here

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 logo

FranConnect gotchas

High

API access token expires in 12 hours with 30-day refresh window

Medium

Rate limit of 73,000 requests per hour per tenant and user

Medium

CSV import enforces strict date and character formatting

Medium

Not all modules have documented REST API endpoints

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Franchise-specific objects have no Nutshell equivalent

    FranConnect's core data model (Units, Territories, Franchisees, Royalty Manager, Training, Segments) has no native counterpart in Nutshell, which is a standard sales CRM. We handle this by migrating Units as Accounts with structured notes, Territories as custom fields, Franchisees as Person+Account splits, Royalty records as a structured CSV export attached to Accounts, and Training as notes on Person records. The customer must validate this flattening during reconciliation. This is not data loss but a structural change that requires business sign-off before production migration.

  • FranConnect OAuth tokens expire in 12 hours during extraction

    FranConnect's access tokens expire 12 hours after issuance, with a 30-day refresh window. For large extractions spanning multiple days, we schedule proactive token refreshes using the stored refresh token. If a refresh token exceeds 30 days, re-authentication with FranConnect credentials is required. We flag this risk during scoping and build the extraction schedule to complete within the 12-hour window for typical record volumes, with a contingency re-auth step if the window is exceeded.

  • Nutshell API rate limits constrain large engagement migrations

    Nutshell's API enforces rate limits on write operations (creating People, Accounts, Leads, Activities). For large engagement histories exceeding 50,000 activity records, we paginate inserts, implement retry logic with exponential backoff, and run overnight batches to stay within limits. We do not disable Nutshell's rate limit controls; we work within them to avoid triggering account-level throttling during migration.

  • Nutshell custom field type constraints require pre-migration validation

    Nutshell supports specific custom field types: text (225 char short text), long text, currency, date, and dropdown. FranConnect custom fields with unsupported types (multi-checkbox, rich text, formula fields, or computed fields) cannot migrate directly. We audit all custom field types during discovery, flag unsupported FranConnect field types, and either drop them from the mapping (with documentation) or suggest a Nutshell-supported equivalent before migration begins.

Migration approach

Six steps for a successful FranConnect to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

FranConnect logo

FranConnect

Source

Strengths

  • Purpose-built for the entire franchise lifecycle from development through operations
  • Multi-location command center with real-time KPI dashboards across all units
  • REST API available for several modules with documented endpoints and OAuth authentication
  • Automated lead capture and drip campaign management with responsive support team
  • Performance benchmarking data showing 2.1x growth advantage for FranConnect customers

Weaknesses

  • Enterprise pricing without free trial or published tiers creates procurement friction
  • Navigation complexity — steep learning curve reported by new users on G2 reviews
  • Platform can experience performance slowdowns during peak usage hours
  • Switching costs are high due to franchise-specific data model tightly coupled to FranConnect conventions
  • Limited public API documentation for all modules — some modules lack documented export endpoints
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across FranConnect and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    FranConnect: Not publicly documented.

  • Data volume sensitivity

    A

    FranConnect exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your FranConnect to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about FranConnect to Nutshell data migrations

Answers to the questions buyers ask most during FranConnect to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your FranConnect to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between two and three weeks for accounts under 5,000 Contacts and 2,000 Leads with clean field mappings and no large franchise-specific data volumes. Migrations with Units, Territories, Royalty records, or large Training histories move to five to eight weeks because of the custom object restructuring, structured CSV exports for financial data, and reconciliation work to represent franchise hierarchies in Nutshell's flat Account model.

Adjacent paths

Related migrations to explore

Ready when you are

Move from FranConnect.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day