CRM migration

Migrate from Freshsales to Nutshell

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

Freshsales logo

Freshsales

Source

Nutshell

Destination

Nutshell logo

Compatibility

89%

8 of 9

objects map 1:1 between Freshsales and Nutshell.

Complexity

BStandard

Timeline

1-2 weeks

Rollback included Accuracy guarantee Field-level validation

Try the reverse

Nutshell
Freshsales

Overview

What this migration involves

Moving from Freshsales to Nutshell is a consolidation migration with a structural twist: Freshsales uses separate Leads and Contacts objects with lifecycle stages, while Nutshell consolidates both into a single People object with a Party Type property. We run the merge logic during the transform phase, mapping Freshsales Leads with lifecycle stages to Nutshell People with the appropriate party_type value, and Freshsales Contacts to Nutshell People with the contact party_type. We preserve the original Freshsales lifecycle stage in a custom field for audit and reporting continuity. Pipeline stage definitions migrate from Freshsales Deal pipelines to Nutshell lead stages, and we handle the owner lookup resolution by email match across both user tables. We do not migrate Freshsales Sequences, Workflows, or Freddy AI scoring as code; we deliver a written inventory of each for the customer's admin to rebuild in Nutshell. Storage limits differ materially between the platforms and we flag any projected overages before migration day.

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

Freshsales logo

Freshsales

What's pushing teams away

  • The UI is described as difficult to navigate with poor documentation on integrations, and reporting lacks the depth available in HubSpot.
  • AI features like Freddy AI scoring and deal predictions are locked behind the Pro $39/user/month tier despite heavy marketing of AI capabilities.
  • Bot sessions are limited to 500 one-time with no monthly refresh, and phone calls incur per-minute charges that add up for global teams.
  • Post-migration from Freshsales Classic, outgoing emails are disabled, workflows and sequences do not execute, and DNS records must be reconfigured.

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 Freshsales objects map to Nutshell

Each row shows how a Freshsales 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.

Freshsales

Lead

maps to

Nutshell

People (party_type = lead)

1:1
Fully supported

Freshsales Leads map to Nutshell People records with party_type set to lead. We extract the Freshsales lifecycle_stage property and preserve it in a custom field fs_original_lifecycle__c on the Nutshell People record for reporting continuity. Lead source, owner, and any custom fields migrate as standard Nutshell fields or custom fields depending on the Nutshell plan. This mapping runs before the Contact import so that the People records are available for deduplication.

Freshsales

Contact

maps to

Nutshell

People (party_type = contact)

1:1
Fully supported

Freshsales Contacts map to Nutshell People records with party_type set to contact. The associated Freshsales Account becomes a Nutshell Company record created first, then linked to the People record via the company relationship. Contact lifecycle stage migrates to the custom field fs_original_lifecycle__c on the Nutshell People record alongside the Lead mapping above.

Freshsales

Account

maps to

Nutshell

Company

1:1
Fully supported

Freshsales Account records map 1:1 to Nutshell Company records. Domain from Freshsales website field becomes the Nutshell Company domain field. Companies are migrated before People so that the company-people relationship is established at Contact insert time. Account address fields map to Nutshell Company address fields with multi-line address formatting preserved.

Freshsales

Deal

maps to

Nutshell

Lead

1:1
Fully supported

Freshsales Deals map to Nutshell Lead records, which in Nutshell carry deal-specific fields including amount, stage, and owner. The Freshsales pipeline becomes a Nutshell lead status or pipeline stage configuration. We map dealstage from Freshsales to the equivalent Nutshell stage name, and preserve probability and amount fields. Closed-won and closed-lost reasons from Freshsales custom fields map to Nutshell custom fields on the Lead.

Freshsales

Pipeline

maps to

Nutshell

Lead Status / Pipeline Configuration

lossy
Fully supported

Freshsales multiple deal pipelines (Pro and above) map to Nutshell pipeline configurations or lead status values. Stage names, probabilities, and stage order migrate as Nutshell stage definitions. If the customer uses more than one Freshsales pipeline, we create the equivalent Nutshell pipeline configuration and map stage probabilities to match the source.

Freshsales

Product

maps to

Nutshell

Product

1:1
Fully supported

Freshsales Products map to Nutshell Products. Product name, SKU (fs_sku), price, and description migrate directly. Products are created before any Deal or Quote import so that the product relationship is satisfied at insert time.

Freshsales

Activity: Task

maps to

Nutshell

Activity

1:1
Fully supported

Freshsales Tasks map to Nutshell Activities linked to the target People or Lead record. Task status, priority, due date, and description migrate directly. Owner mapping resolves by email match against Nutshell users. Activities are imported after People and Leads to satisfy the parent record lookup.

Freshsales

Activity: Event / Call

maps to

Nutshell

Activity

1:1
Fully supported

Freshsales Events (meetings and calls) map to Nutshell Activities. Call duration, disposition, and meeting location fields migrate to Nutshell Activity fields. Call recordings stored in Freshsales do not migrate as files; we document the recording URL in a custom Activity field and the customer configures recording access post-migration.

Freshsales

Custom Field

maps to

Nutshell

Custom Field

1:1
Fully supported

Freshsales custom fields on Leads, Contacts, Accounts, and Deals map to Nutshell custom fields on the corresponding People, Company, and Lead records. We validate field type compatibility during scoping and flag any Freshsales advanced custom fields that may have been gated by plan tier. Text, number, date, dropdown, and checkbox field types map directly; multi-select picklists map to Nutshell multi-select fields.

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.

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

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

  • Freshsales Sequences do not auto-execute post-migration

    Freshsales Sales Sequences (available on Pro and above at $39/user/month) require Freshworks support to re-enable after any account-level migration. Outgoing emails are automatically disabled and sequence execution halts. We flag all active Freshsales sequences during scoping, document their step definitions and cadence, and deliver a written sequence inventory so the customer's admin can rebuild them as Nutshell email sequences post-migration. We do not migrate sequences as executable code.

  • Freddy AI scores have no Nutshell equivalent

    Freddy AI contact and deal scoring in Freshsales is Pro-tier only and generates machine-learning-based lead scores that do not transfer to any Nutshell field natively. We preserve the numeric score value in a custom field on the migrated People record (fs_freddy_score__c) but the score logic does not update post-migration. Customers relying on Freddy AI for prioritization should rebuild scoring criteria in Nutshell using standard field rules or a third-party enrichment tool.

  • Storage limits can silently restrict migration scope

    Freshsales storage limits vary by plan: 2GB per user on Growth, 5GB per user on Pro, 100GB per user on Enterprise. Nutshell includes unlimited data storage on all paid plans. However, if the source Freshsales account is approaching or has exceeded its storage limit, attachments and file uploads may not fully export. We sample attachment sizes during scoping and alert if projected file volume exceeds what the Freshsales export can capture.

  • Freshsales uses per-minute phone billing with no cap

    Freshsales built-in telephony charges per minute for outbound calls (approximately $0.02 per minute US domestic, higher internationally). Call records migrate as Activity metadata but call recording audio files require Enterprise-tier audit log access. We flag call record and recording volume during scoping so the customer can assess whether Nutshell's bundled communication features (or a third-party telephony integration) are more cost-effective post-migration.

  • Lead custom field mapping during conversion requires pre-planning

    Freshsales supports mapping custom fields during Lead-to-Contact conversion via Admin settings, but if the customer has custom lead fields that are not mapped at conversion time, those values are lost. We extract all Freshsales Lead custom fields during scoping and verify whether conversion mapping is configured before migration. Any unmapped lead fields are flagged for manual handoff to the customer admin for post-migration action.

Migration approach

Six steps for a successful Freshsales to Nutshell data migration

  1. Discovery and scoping

    We audit the source Freshsales account across plan tier (Growth/Pro/Enterprise), record counts for Leads, Contacts, Accounts, Deals, Products, Activities, and any active Custom Objects. We extract custom field definitions and validate plan-gating for advanced fields. We identify active Sales Sequences and Workflows requiring rebuild documentation. We assess storage usage against Freshsales plan limits and flag any attachment volume risk. The discovery output is a written migration scope and a custom field mapping matrix.

  2. Schema design and Nutshell field provisioning

    We design the destination Nutshell schema including custom fields on People, Company, and Lead objects, stage definitions for the lead pipeline, and any custom field types (multi-select, date, number). We provision custom fields in Nutshell before any data import using the Nutshell field settings API. If the customer uses multiple Freshsales Deal pipelines, we configure the equivalent Nutshell pipeline structure at this stage.

  3. Test migration and reconciliation

    We run a test migration with a representative sample (typically 100-200 records per object type) into the Nutshell destination account. The customer reconciles record counts, spot-checks mapped fields, and verifies that the People-party_type split is producing the expected Lead versus contact distribution. Any mapping corrections are made before the full production migration begins. Freshsales sequences and workflow inventory are documented and delivered at this stage.

  4. Owner and user reconciliation

    We extract every distinct Freshsales Owner referenced across Leads, Contacts, Accounts, Deals, and Activities and match by email against the Nutshell destination account's user list. Any Freshsales Owner without a matching Nutshell user goes to a reconciliation queue for the customer's admin to provision. Owner lookups must be resolved before any record import that references them.

  5. Production migration in dependency order

    We run production migration in dependency order: Companies (from Freshsales Accounts), People records (Leads and Contacts merged via the party_type split), Leads with deal data, Products, Activities (Tasks and Events with owner resolved), and Custom Fields last. Each phase emits a row-count reconciliation report. We use Nutshell's API import endpoints with rate-limit handling and exponential backoff for all object types.

  6. Cutover, delta sync, and rebuild handoff

    We freeze Freshsales writes during cutover, run a final delta migration of records modified during the migration window, and hand off the sequence and workflow inventory document to the customer's admin team. We support a one-week hypercare window for reconciliation issues. We do not rebuild Freshsales Sequences or Workflows in Nutshell inside the migration scope; that work is covered by the delivered inventory document.

Platform deep dives

Context on both ends of the pair

Freshsales logo

Freshsales

Source

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.
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. 3 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 Freshsales and Nutshell.

  • Object compatibility

    B

    3 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

    Freshsales: Not publicly documented on Freshworks CRM; Freshdesk docs reference rate limits but Freshsales-specific limits are undocumented.

  • Data volume sensitivity

    B

    Freshsales doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Freshsales 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 Freshsales to Nutshell data migrations

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

Can't find your answer?

Walk through your Freshsales 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 one and two weeks for accounts under 10,000 Contacts and 3,000 Deals with a single pipeline and a straightforward custom field set. Migrations with multiple Deal pipelines, large custom field sets, high attachment volumes, or active Sales Sequences requiring rebuild documentation extend to two to four weeks. The timeline also depends on how quickly the customer approves the test migration sample and resolves any owner reconciliation gaps.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Freshsales.
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