CRM migration
Field-level mapping, validation, and rollback between eZnet CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
eZnet CRM
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between eZnet CRM and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
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.
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 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
Nutshell
Company
1:1eZnet 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
Nutshell
People
1:1eZnet 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
Nutshell
Lead
1:1eZnet 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
Nutshell
Deal
1:1eZnet 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
Nutshell
Pipeline (on Deal)
lossyeZnet 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)
Nutshell
Activity
1:1eZnet 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)
Nutshell
Attachment (on Company or People)
1:1eZnet 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
Nutshell
Custom Fields
lossyeZnet 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.
| eZnet CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Account | Company1:1 | Fully supported | |
| Contact | People1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Pipeline | Pipeline (on Deal)lossy | Fully supported | |
| Activity (calls, emails, tasks, events) | Activity1:1 | Fully supported | |
| Document (metadata) | Attachment (on Company or People)1:1 | Fully supported | |
| Custom Fields | Custom Fieldslossy | Mapping required |
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.
eZnet CRM gotchas
Per-tier record limits create migration scope boundaries
No publicly documented API endpoint reference
Sparse public review corpus limits migration risk assessment
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 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.
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.
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.
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.
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.
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
eZnet CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 eZnet CRM and Nutshell.
Object compatibility
3 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
eZnet CRM: Not publicly documented.
Data volume sensitivity
eZnet CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
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 eZnet CRM to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave eZnet CRM
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.