CRM migration

Migrate from FreeCRM to Nutshell

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

FreeCRM logo

FreeCRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

89%

8 of 9

objects map 1:1 between FreeCRM and Nutshell.

Complexity

CModerate

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

FreeCRM has no documented public API, so every migration runs through their CSV import/export tooling. This shapes the entire approach: we discover every active template set during scoping, normalize template-driven custom fields into standard CRM properties before writing, and coordinate export file sizes to avoid free-tier storage throttles. Nutshell accepts Contacts, Companies, and Deals via its API or CSV loader with custom fields supported on People, Companies, and Leads. We map FreeCRM's free-text stage values to Nutshell pipeline columns, split comma-separated tags into Nutshell's tag format, and resolve the owner-to-user lookups by email. Workflow automations, sequences, and any custom objects built inside FreeCRM do not migrate; we deliver a written inventory of these for the customer's admin to rebuild in Nutshell.

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

FreeCRM logo

FreeCRM

What's pushing teams away

  • Reviewers report limited ability to customize and report, with core functionality gated behind the paid tier.
  • Lack of integrations with common email programs and financial software forces teams to manually move data between systems.
  • Storage and feature caps in the free tier create bottlenecks as team size or contact volume grows.
  • Users switched to proprietary or agency-provided CRMs specifically to get better integrations with their daily workflow tools.
  • Reporting limitations mean teams cannot generate meaningful sales analytics without manual spreadsheet work.

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

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

FreeCRM

Contact

maps to

Nutshell

Person

1:1
Fully supported

FreeCRM Contact records export with standard fields (name, email, phone, address) via CSV. These map directly to Nutshell Person records. We preserve the related-to Company link by resolving the parent FreeCRM Company name against the Nutshell Account before Contact insert, satisfying the lookup at migration time.

FreeCRM

Company

maps to

Nutshell

Account

1:1
Fully supported

FreeCRM Company records export with name, domain, and industry fields intact. These map to Nutshell Account records. The Account is created before any Person import so that the Person-to-Account relationship is resolved at insert time rather than requiring a post-migration reconciliation pass.

FreeCRM

Lead

maps to

Nutshell

Lead

1:1
Fully supported

FreeCRM Lead records use the template system so field names vary by account. We extract the complete field set during discovery, then normalize lead-status and lead-source fields into Nutshell's standard Lead fields. Any FreeCRM custom properties on Leads that have no Nutshell equivalent become Nutshell custom fields on the Lead object, which Nutshell supports on all paid tiers.

FreeCRM

Deal

maps to

Nutshell

Account (related Deal)

1:1
Fully supported

FreeCRM Deal records export with amount, stage, and expected close date. Stage values are stored as free text per FreeCRM's Kanban setup. We extract the full stage list during discovery, map each free-text stage to a corresponding Nutshell pipeline column during migration, and preserve the deal-to-account link by resolving the parent FreeCRM Company name.

FreeCRM

Pipeline Stage

maps to

Nutshell

Pipeline Column

lossy
Fully supported

FreeCRM uses a Kanban board with account-defined stage names rather than a structured stage object. We inventory every distinct stage value in the FreeCRM export, configure matching Nutshell pipeline columns in the destination account during the pre-migration setup phase, and map each FreeCRM stage value to the corresponding Nutshell column by name match or customer-confirmed mapping.

FreeCRM

Activity (Task, Event, Call Log)

maps to

Nutshell

Activity

1:1
Fully supported

FreeCRM tasks, events, and call logs export as activity records with a related-to link to Contact or Company and a timestamp. We preserve the related-to link and timestamp in Nutshell's activity model. Note that the activity sequence ordering may not be complete for accounts with high activity density due to the flat nature of CSV exports.

FreeCRM

Custom Fields (template-driven)

maps to

Nutshell

Custom Fields

1:1
Fully supported

FreeCRM custom fields are defined per-record via templates and vary by account. This is the highest-severity migration risk. We inventory every custom field across all active templates during discovery, normalize each into a Nutshell custom property on the appropriate object (Person, Account, or Lead), and document the mapping in a field-level export. Fields with no Nutshell equivalent are flagged for the customer to review during scoping.

FreeCRM

Tags

maps to

Nutshell

Tags

1:1
Mapping required

FreeCRM exports tags as comma-separated values on Contact and Company records. We split them into individual tag values and map them to Nutshell's tag format, which attaches to Person and Account records. The customer confirms tag strategy during scoping if the FreeCRM account uses tags for both contact classification and content labeling.

FreeCRM

Users/Owners

maps to

Nutshell

Users

1:1
Mapping required

FreeCRM user accounts exist but owner assignment on records is not always consistently populated across the export. We extract distinct owner email addresses from FreeCRM and map them to Nutshell User records by email match. Any FreeCRM owner without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

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.

FreeCRM logo

FreeCRM gotchas

High

Template-driven fields vary per account

High

Free tier storage and feature caps are undocumented

Medium

Workflow automations do not export

Medium

No documented public API

Medium

Invoice and campaign data only in Pro 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

  • FreeCRM template fields have no global schema

    FreeCRM's template-driven data model means every account has a unique field structure. There is no standard field list we can assume. We inventory every template in use during the discovery phase and build a per-account field map before writing any destination records. Skipping this step results in silent field drops. If FreeCRM account has five templates with different field sets, we produce five separate field maps. This step adds scope time that flat-schema CRMs do not require.

  • Free tier storage caps are undocumented and can abort exports mid-run

    FreeCRM's free tier imposes limits on storage and feature availability but these limits are not published. We have encountered accounts where contact or attachment storage silently throttled without warning during export. During export scoping we confirm available storage headroom, request a pre-export storage report from FreeCRM if accessible, and chunk large exports to avoid hitting the cap mid-run. Accounts with heavy attachment loads may need to migrate attachments separately or accept that some attachments cannot be exported from the free tier.

  • FreeCRM has no documented public API

    Data migration from FreeCRM runs entirely through their CSV import/export tooling. There is no REST API with rate limits, pagination, or webhook support. Large datasets may require chunking the export into multiple files, then re-assembling the field maps during transformation. We coordinate export file sizes with the customer before initiating migration, and any export file larger than 50,000 records is split into batches to avoid export timeout failures.

  • Workflow automations and sequences do not export

    FreeCRM supports workflow automation including follow-up sequences and stage-change triggers. These are not exposed via CSV export or any documented API endpoint. We flag every active automation during discovery so the customer knows which business logic must be rebuilt manually in Nutshell. Nutshell's sales automation features vary by plan tier, so the rebuild scope depends on which Nutshell tier the customer selects.

  • FreeCRM stage values are free text, not structured enumeration

    FreeCRM pipeline stages are account-defined text values rendered in the Kanban view, not a structured stage object. Two FreeCRM accounts can have stages named 'Proposal' that map to different positions in the pipeline. We extract every distinct stage value during discovery, present the customer with a stage-mapping worksheet, and configure Nutshell pipeline columns to match before any Deal records are written.

Migration approach

Six steps for a successful FreeCRM to Nutshell data migration

  1. Discovery and template inventory

    We audit the FreeCRM account for all active templates, export field lists per template, inventory pipeline stage names, list active workflows, and assess storage headroom. We confirm the FreeCRM account tier (Free or Pro) to determine whether invoice data, unlimited campaigns, or advanced reporting fields are present. The discovery output is a written migration scope including the full template inventory, per-template field maps, stage list, and a storage headroom assessment.

  2. Nutshell account setup and schema design

    We configure the Nutshell destination account: creating custom fields on Person, Account, and Lead to match any FreeCRM template fields that have no standard Nutshell equivalent; configuring pipeline columns to match the discovered FreeCRM stage list; and setting up the Nutshell user accounts corresponding to the FreeCRM owners extracted from the export. Nutshell's Settings > Data > Import tool supports custom field mapping, which we use alongside direct API writes for complex transformations.

  3. CSV export coordination and data extraction

    We coordinate the CSV export with the customer, requesting exports in manageable batches if the record count exceeds 50,000 rows per object. We extract Contacts, Companies, Leads, Deals, and Activities from FreeCRM's CSV export tooling. Any attachment URLs are extracted separately for reassembly in Nutshell if the export captures them. We flag any records that hit free-tier storage throttling and escalate to the customer for resolution before proceeding.

  4. Transformation and field normalization

    We apply the per-template field maps produced during discovery, splitting comma-separated tags into individual values, normalizing date formats to ISO 8601, resolving FreeCRM owner email addresses to Nutshell User lookups, and applying the stage-mapping worksheet to Deal records. Any custom object or template-specific fields that have no Nutshell equivalent are written to Nutshell custom fields with a naming convention that preserves the original FreeCRM field label for the customer's reference.

  5. Sandbox import and reconciliation

    We run a trial import into a Nutshell test account or sandbox equivalent using production-like data volume. The customer reconciles record counts across all objects, spot-checks 20-30 records for field-level accuracy, and validates that related-to links (Person-to-Account, Deal-to-Account) resolved correctly. Mapping corrections are documented and applied to the production import script before cutover.

  6. Production migration and cutover

    We run production migration in dependency order: Accounts first (from FreeCRM Companies), then Persons (with AccountId resolved), then Leads (with custom fields applied), then Deals (with stage mapping applied and AccountId resolved), then Activities (with related-to links resolved). Owner lookups that lack a matching Nutshell User are held until the customer provisions the missing accounts. We freeze FreeCRM writes during cutover and run a final delta migration for any records modified during the window.

  7. Workflow inventory handoff and post-migration support

    We deliver a written inventory of every active FreeCRM workflow and automation with its trigger conditions, actions, and a recommended Nutshell equivalent based on the destination tier. We support a one-week hypercare window where we resolve reconciliation issues raised by the customer's team. We do not rebuild FreeCRM workflows as Nutshell sales automation rules inside the migration scope; that work is handled by the customer's admin or a separate Nutshell implementation engagement.

Platform deep dives

Context on both ends of the pair

FreeCRM logo

FreeCRM

Source

Strengths

  • Free-forever tier with no per-user cost lowers the barrier to first-time CRM adoption.
  • Template-driven record customization lets small businesses shape fields without developer help.
  • Cloud-hosted with iOS and Android apps, removing IT setup overhead.
  • Contact, lead, and basic deal tracking covered without training for non-technical users.
  • Useful entry-level option for teams not currently running an all-encompassing CRM.

Weaknesses

  • Customization and reporting are gated behind paid tiers, capping the value of the free plan quickly.
  • Limited integrations with mainstream email and accounting tools force manual data movement.
  • Storage and feature caps in the free tier create bottlenecks as contact volume grows.
  • Reporting is too thin for meaningful sales analytics without exporting to spreadsheets.
  • Reviewers cite switching to proprietary or agency-provided CRMs once integration needs mature.
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?

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

C

Overall complexity

Moderate migration

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

  • Object compatibility

    C

    4 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

    FreeCRM: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most FreeCRM to Nutshell migrations complete in two to three weeks for accounts under 10,000 Contacts and 2,000 Deals with a single template set and no heavy attachment load. Accounts with multiple active FreeCRM templates, a large number of custom fields, or attachment-heavy records requiring chunked CSV handling extend to four to six weeks. The primary timeline driver is template normalization — every unique template set requires a separate field map during discovery before any data is written.

Adjacent paths

Related migrations to explore

Ready when you are

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