CRM migration
Field-level mapping, validation, and rollback between Essential MD Software Suite and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Essential MD Software Suite
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Essential MD Software Suite and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Essential MD Software Suite is a medical-practice-oriented platform that stores person records (contacts and leads), company records, deal/pipeline data, activities, and custom fields for healthcare-adjacent sales and administrative workflows. Nutshell is a small-to-mid-market CRM with People, Companies, Leads, and Deals as its core objects, plus custom fields scoped per record type (Person, Company, Lead) and an open JSON-RPC API for data import and export. The migration carries Essential MD's person records into Nutshell People, companies into Nutshell Companies, deals into Nutshell Deals with pipeline-stage mapping, and all custom fields as Nutshell custom properties. Activities (calls, emails, notes) migrate as Nutshell Tasks and Notes with original timestamps. Essential MD workflows, automation rules, and any healthcare-specific constructs without a direct Nutshell equivalent must be rebuilt — we export the definitions as a reference document for your Nutshell admin. The migration runs against the Essential MD API using paginated reads; Nutshell receives data via its REST API and bulk-import endpoints. Owner resolution uses email matching against existing Nutshell users; unassigned records land in a fallback owner for manual routing.
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 Essential MD Software Suite 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.
Essential MD Software Suite
Person (Contact)
Nutshell
People
1:1Essential MD person records map directly to Nutshell People. Nutshell People store name fields, email, phone, address, and owner. All standard fields migrate as direct mappings; custom person properties migrate as Nutshell custom fields scoped to People. We also preserve the original record creation timestamp in a custom datetime field on the Nutshell People record to maintain historical accuracy.
Essential MD Software Suite
Person (Lead)
Nutshell
Lead
1:manyEssential MD persons with a lead-status flag route to Nutshell Leads. Persons marked as converted contacts route to Nutshell People. The split is based on Essential MD's internal status field; we read the field value at migration time to determine the correct Nutshell target object.
Essential MD Software Suite
Company
Nutshell
Company
1:1Essential MD company records map to Nutshell Companies with direct field correspondence on name, domain/website, address, industry, and employee count. Multi-contact companies collapse to one primary Company record; additional associations are preserved as Nutshell People linked to the Company. The original company create date is stored in a custom datetime field on the Nutshell Company to preserve audit history.
Essential MD Software Suite
Deal
Nutshell
Deal
1:1Essential MD deals map to Nutshell Deals. Nutshell Deal fields (name, value, stage, close date, owner) correspond to Essential MD deal fields. Pipeline and stage names from Essential MD require value mapping to Nutshell's pipeline stage names. Each deal's original create timestamp is recorded in a custom datetime field for reporting continuity.
Essential MD Software Suite
Pipeline
Nutshell
Pipeline
1:1Essential MD pipelines become Nutshell Pipelines. Each Nutshell pipeline has named stages with individual probability weights. We create a matching pipeline in Nutshell for each distinct Essential MD pipeline and map stage names value-by-value. The mapping also transfers any custom stage probability values to the Nutshell stage probability field, preserving the original forecast logic.
Essential MD Software Suite
Pipeline Stage
Nutshell
Stage (on Deal)
1:1Stage names from Essential MD are mapped to Nutshell stage names by value correspondence. Nutshell stages have built-in probability fields; we set these from the destination pipeline configuration or from Essential MD's stage probability metadata if available in the export.
Essential MD Software Suite
Activity (Call, Email, Meeting)
Nutshell
Task
1:1Essential MD activity records (calls, emails, meetings) become Nutshell Tasks. Type field in Nutshell Task is set from the Essential MD activity type. Original timestamps, activity descriptions, and owner links are preserved as task fields. We also capture the original activity duration and attendee information in custom fields to maintain detailed interaction history.
Essential MD Software Suite
Note
Nutshell
Note
1:1Essential MD notes migrate as Nutshell Notes attached to the corresponding Person, Company, or Deal record. Rich-text content is preserved; inline file references are flagged for manual re-upload if the attachment was stored as a linked file. The original note creation date is stored in a custom datetime field to preserve historical context.
Essential MD Software Suite
Custom Object
Nutshell
Custom Fields (on Person/Company/Lead/Deal)
1:1Essential MD custom objects and their fields require Nutshell custom fields to be created on the appropriate object (Person, Company, Lead, or Deal) before migration. We deliver a custom-field creation plan as part of the migration package so Nutshell is schema-ready before data lands.
Essential MD Software Suite
Owner / User
Nutshell
Owner (User lookup on all records)
1:1Essential MD owner IDs are resolved by email match against Nutshell user accounts. Unmatched owners are flagged in a pre-migration report; your team either invites them to Nutshell or assigns records to a designated fallback owner before the migration run.
Essential MD Software Suite
Attachment / File
Nutshell
Attachment (re-upload to Nutshell)
1:1Essential MD file attachments do not have a direct upload API in Nutshell's standard endpoints. Files are downloaded from Essential MD storage, and re-upload links or instructions are provided. For large batches, we include a file manifest so your team can bulk-re-attach in Nutshell after migration.
Essential MD Software Suite
Internal ID / Record UUID
Nutshell
Source_System_ID__c (custom field)
1:1Essential MD record IDs are stored in a custom field on each Nutshell record for traceability, delta-run de-duplication, and cross-reference during reconciliation. This field is created as a read-only text custom field on the target Nutshell object. During the delta-pickup window, this ID field enables precise matching of any updated records to their migrated counterparts.
| Essential MD Software Suite | Nutshell | Compatibility | |
|---|---|---|---|
| Person (Contact) | People1:1 | Fully supported | |
| Person (Lead) | Lead1:many | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Pipeline Stage | Stage (on Deal)1:1 | Fully supported | |
| Activity (Call, Email, Meeting) | Task1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Custom Object | Custom Fields (on Person/Company/Lead/Deal)1:1 | Fully supported | |
| Owner / User | Owner (User lookup on all records)1:1 | Fully supported | |
| Attachment / File | Attachment (re-upload to Nutshell)1:1 | Fully supported | |
| Internal ID / Record UUID | Source_System_ID__c (custom field)1:1 | Fully supported |
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.
Essential MD Software Suite gotchas
Patient ID remapping risk at migration time
Encounter-to-billing linkage integrity
Custom field schema discovery requires manual enumeration
Document export format and size limits
Insurance payer name inconsistency between exports and destination
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
Audit Essential MD data model and build the mapping specification
FlitStack AI reads the Essential MD API to enumerate all person types, companies, deals, pipelines, stages, activities, and custom fields. We build a complete data inventory that identifies every pick-list value, every custom field name and type, and every owner record. The mapping specification maps each Essential MD object and field to its Nutshell equivalent — direct maps, value mappings, and custom-field creation requests are all documented in a schema plan your Nutshell admin executes before migration.
Create Nutshell custom fields from the field-creation plan
Your Nutshell admin (or our team on a delegated-access engagement) creates the custom fields identified in Step 1 on the appropriate Nutshell objects (Person, Company, Lead, Deal). We deliver the exact field names, types, and required flags. This step is the critical path — no records referencing custom fields can migrate until the schema is in place. We also create the Nutshell Pipelines and stage names that correspond to each Essential MD pipeline.
Resolve owners and validate user account coverage
We match Essential MD owner records to existing Nutshell user accounts by email address. The owner audit report shows match rates and flags any Essential MD owner without a Nutshell counterpart. Your team resolves gaps by inviting the missing users to Nutshell or designating a fallback owner for unmatched records. No record migrates without a resolved owner reference. If necessary, we can schedule a follow‑up review to confirm the owner list is complete before the migration window opens.
Run a sample migration with field-level diff
A representative slice of records — typically 100–500 covering persons, companies, deals, activities, and a sample of each custom field type — migrates first. We generate a field-level diff comparing source values against the Nutshell record so you can verify pick-list value mapping, custom field population, and pipeline-stage routing before the full run commits. The diff highlights any mismatches in stage names, missing custom field values, or owner assignments, giving your team a clear checklist for corrections before the main migration.
Execute full migration with delta-pickup window
The full migration reads all remaining records from Essential MD in paginated batches, transforms each record according to the mapping specification, and inserts into Nutshell via the API. A delta-pickup window (typically 24–48 hours) captures any Essential MD records modified during the cutover. An audit log records every operation, and one-click rollback is available if reconciliation fails. The migration platform monitors API response times and automatically retries failed inserts, ensuring high reliability even for large data volumes.
Platform deep dives
Essential MD Software Suite
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Essential MD Software Suite and Nutshell.
Object compatibility
2 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
Essential MD Software Suite: Not publicly documented.
Data volume sensitivity
Essential MD Software Suite 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 Essential MD Software Suite to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Essential MD Software Suite 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 Essential MD Software Suite
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.