CRM migration

Migrate from eZnet CRM to Nutshell

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

eZnet CRM logo

eZnet CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between eZnet CRM and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from eZnet CRM to Nutshell is a migration from a niche, budget-focused CRM with minimal public tooling support to a mainstream small-business CRM with documented import pathways and Google Workspace and Microsoft 365 native sync. eZnet CRM organizes data around Accounts, Contacts, Leads, and Opportunities; Nutshell uses Companies, People, Leads, and Deals with a flatter activity model. We resolve the eZnet Account-Contact-Opportunity hierarchy into Nutshell's Companies-People-Deals structure during scoping, extract all available fields via eZnet's export mechanisms, and feed the result into Nutshell's CSV import or API-based migration workflow. eZnet CRM's Standard tier carries a 100,000-record cap that we confirm against during discovery. Workflows, email marketing campaigns, and document library metadata do not migrate as code; we deliver a written inventory 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

eZnet CRM logo

eZnet CRM

What's pushing teams away

  • Very limited public review presence makes it difficult to assess real-world reliability and support quality before committing.
  • Low web traffic and market visibility suggest a small customer base, which raises long-term viability and ecosystem concerns.
  • Feature documentation is sparse, making it hard for teams to evaluate whether specific capabilities (like complex workflow automation) meet their needs.
  • Smaller vendor footprint means fewer third-party integrations and a thinner marketplace compared to established CRM competitors.

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

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

eZnet CRM

Account

maps to

Nutshell

Company

1:1
Fully supported

eZnet CRM Accounts map directly to Nutshell Companies. Account name becomes the Company name, and account address fields map to the Nutshell mailing address fields. The Company becomes the parent record before any related People (contacts) are imported so that the People-Company relationship is satisfied at the time of insert. Account phone and website migrate as standard Company fields.

eZnet CRM

Contact

maps to

Nutshell

People

1:1
Fully supported

eZnet CRM Contacts map to Nutshell People. Name, email, phone, and address fields migrate directly. The Contact-Account link becomes the People-Company link in Nutshell, resolved at migration time by matching the parent Account name to the destination Company. Any Contact without a parent Account is held in a reconciliation batch for the customer to resolve before final import.

eZnet CRM

Lead

maps to

Nutshell

Lead

1:1
Fully supported

eZnet CRM Leads map to Nutshell Leads. Lead status, source, and custom lead fields transfer to equivalent Nutshell Lead fields. eZnet CRM Lead records that represent unqualified prospects stay as Nutshell Leads rather than converting to People, preserving the lead qualification context for the sales team to work through after cutover.

eZnet CRM

Opportunity

maps to

Nutshell

Deal

1:1
Fully supported

eZnet CRM Opportunities map to Nutshell Deals. Deal name, amount, expected close date, and stage migrate directly. The pipeline and stage order from eZnet CRM's Opportunity configuration becomes a Nutshell pipeline with corresponding stages. Closed-won and closed-lost reasons from eZnet CRM custom fields become Deal custom fields in Nutshell.

eZnet CRM

Pipeline

maps to

Nutshell

Pipeline (on Deal)

lossy
Fully supported

eZnet CRM pipeline configuration (stage names, stage order, win/loss definitions) migrates as a Nutshell Deal pipeline. We capture the full stage list and their sequence, then configure the destination pipeline in Nutshell before Deals are imported so that stage assignments resolve correctly at import time.

eZnet CRM

Activity (calls, emails, tasks, events)

maps to

Nutshell

Activity

1:1
Fully supported

eZnet CRM Activities map to Nutshell Activity records on the relevant Company, People, or Deal. Activity type, date, notes, and owner transfer to the Nutshell timeline. Nutshell merges activity types into a unified timeline rather than separate object types, so we consolidate the eZnet activity type into a type label field that Nutshell's activity display renders correctly.

eZnet CRM

Document (metadata)

maps to

Nutshell

Attachment (on Company or People)

1:1
Fully supported

eZnet CRM Document Library metadata (file name, description, associated Account or Contact) migrates as Nutshell attachments on the linked Company or People record. File blobs require separate handling; we export them as a file package and flag them for the customer to re-attach manually or via Nutshell's file upload during post-migration setup.

eZnet CRM

Custom Fields

maps to

Nutshell

Custom Fields

lossy
Mapping required

eZnet CRM custom fields on Accounts, Contacts, Leads, and Opportunities are captured with their full schema (field label, data type, picklist values) and reconstructed in Nutshell as custom fields on the equivalent objects. Picklist values in eZnet CRM map to Nutshell drop-down field options. The custom field reconstruction happens before data import so that incoming records pass Nutshell's field validation.

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.

eZnet CRM logo

eZnet CRM gotchas

High

Per-tier record limits create migration scope boundaries

High

No publicly documented API endpoint reference

Medium

Sparse public review corpus limits migration risk assessment

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

  • eZnet CRM has no public API reference for programmatic export

    eZnet CRM does not publish a developer portal or documented REST API, which means migration tooling cannot rely on API calls to extract data. We assess available export mechanisms during discovery, which may include CSV exports, file-based data dumps, or manual extraction with customer-provided credentials. This adds scoping time compared to migrations from platforms with documented APIs, and any automated extraction paths must be validated in a pre-migration test before full data extraction begins.

  • eZnet CRM Standard tier record cap may block migration

    The Standard tier of eZnet CRM enforces a 100,000-record organizational limit. We confirm the customer's current record count during scoping. If the total exceeds 100K and the account is on Standard, we flag the migration as blocked and recommend upgrading to Professional (which removes the cap) before extraction proceeds. This check applies to both total record count and per-object counts where eZnet CRM enforces sub-limits.

  • Contact-to-Account relationship resolution requires pre-import ordering

    eZnet CRM links Contacts to Accounts; Nutshell links People to Companies. The relationship must be resolved before People import so that each People record has a valid Company reference. We extract Accounts first, create Companies in Nutshell, then extract Contacts and map them to the corresponding Companies before inserting People. Records without a parent relationship in eZnet CRM are flagged for the customer to assign during reconciliation.

  • Document file blobs require separate handling outside standard migration

    eZnet CRM's Document Library stores file blobs (PDFs, spreadsheets, images) linked to Account records. Nutshell does not have an equivalent document library object; attachments live on individual records. We export document metadata and link it to the parent Company in Nutshell, but the actual file blobs require a separate file transfer step that the customer approves during scoping. This is flagged as an out-of-scope item unless a specific file migration add-on is negotiated.

Migration approach

Six steps for a successful eZnet CRM to Nutshell data migration

  1. Discovery and export feasibility assessment

    We audit the source eZnet CRM account across tier (Standard, Professional, Enterprise), record counts per object, available export mechanisms, custom field schema, and pipeline configuration. Because eZnet CRM lacks a documented public API, we test available export paths (CSV, direct database query if permitted, or manual extraction) during discovery before committing to a migration approach. We also confirm the customer's Nutshell account is provisioned and identify any Nutshell custom fields that need pre-creation.

  2. Schema design and custom field reconstruction

    We design the Nutshell destination schema before data extraction. This includes creating any custom fields on Nutshell People, Companies, Leads, and Deals that correspond to eZnet CRM custom fields, matching data types (text, number, date, drop-down) and drop-down option lists. Pipeline stages from eZnet CRM are configured as a Nutshell Deal pipeline with equivalent stage names and ordering. The schema design is documented in a field mapping sheet reviewed by the customer before extraction begins.

  3. Test export and data quality audit

    We run a test extraction of a sample dataset (typically 50-100 records per object) to validate the export mechanism, confirm field coverage, and identify any data quality issues (missing required fields, inconsistent formats, duplicate records). Data quality findings are reported to the customer with a recommended cleanup phase before full extraction. This step is critical given eZnet CRM's sparse documentation and the likelihood of legacy data accumulated over years of use.

  4. Full data extraction and transformation

    We run the full extraction of Accounts, Contacts, Leads, Opportunities, Activities, and Documents metadata in dependency order. Accounts are extracted first to establish the Company parent records. Contacts are extracted with their parent Account reference and transformed to carry the corresponding Nutshell Company name as a lookup key. Opportunities are extracted with their parent Account and owner references. Activities are extracted as a separate batch with their parent record reference carried forward.

  5. Production import and reconciliation

    We import into the production Nutshell environment in record-dependency order: Companies (from Accounts), People (from Contacts with CompanyId resolved), Leads, Deals (with pipeline and stage resolved), and Activities (linked to the correct Company, People, or Deal). Each phase emits a row-count reconciliation report showing records imported, skipped, and errored. The customer spot-checks a sample of records against the source before sign-off.

  6. Cutover and documentation handoff

    We freeze eZnet CRM writes during cutover, run a final delta migration of any records created or modified during the migration window, then mark Nutshell as the system of record. We deliver a written inventory of eZnet CRM workflows, email marketing campaigns, and document library contents for the customer's admin to rebuild in Nutshell. We support a three-day post-cutover window to resolve data issues raised by the team. We do not rebuild automations as Nutshell workflows inside the migration scope.

Platform deep dives

Context on both ends of the pair

eZnet CRM logo

eZnet CRM

Source

Strengths

  • Starting price of $10/user/month is among the lowest entry points for a cloud CRM with integrated marketing and support.
  • All-in-one bundling of sales, marketing, and support reduces the need for multiple subscriptions.
  • Unlimited records on Professional and Enterprise tiers remove per-database storage concerns for growing teams.
  • Customization capabilities including custom fields, modules, and dashboards provide flexibility for non-standard workflows.
  • Private Cloud option with on-site hosting and free installation appeals to organizations with data residency requirements.

Weaknesses

  • Extremely thin public review presence makes independent quality assessment nearly impossible.
  • Monthly web traffic is extremely low, indicating a very small customer base and limited market traction.
  • No dedicated API documentation or developer portal found in public research, raising questions about migration tooling support.
  • Sparse official documentation and FAQ content suggests limited investment in customer-facing resources.
  • No evidence of a mature third-party integration marketplace compared to established CRM platforms.
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 eZnet CRM 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

    eZnet CRM: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your eZnet CRM 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 four weeks for accounts under 10,000 records with straightforward object mapping and no complex custom field dependencies. Migrations with large activity histories, multiple custom field sets, or inventory data move to five to nine weeks because of file-based export handling, relationship reconciliation, and Nutshell import validation cycles. eZnet CRM's lack of a public API adds scoping time compared to migrations from platforms with documented REST endpoints.

Adjacent paths

Related migrations to explore

Ready when you are

Move from eZnet CRM.
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