CRM migration

Migrate from Essential MD Software Suite to Nutshell

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 logo

Essential MD Software Suite

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Essential MD Software Suite and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Essential MD Software Suite logo

Essential MD Software Suite

What's pushing teams away

  • Practices outgrow the platform when they expand to multi-location operations, add new specialties, or require advanced analytics that the suite does not provide.
  • Integration limitations with modern third-party tools such as telehealth platforms, patient portals, and modern clearinghouses drive teams to platforms with broader API ecosystems.
  • Users report frustration with outdated UI and slower development velocity compared to newer cloud-native medical platforms that ship features more frequently.
  • Scaling challenges emerge when practices need to manage higher patient volumes, more complex insurance workflows, or value-based care contracts that require data the platform cannot easily surface.
  • Data portability concerns arise when practices want to leave, as the export tooling may produce formats that require manual reconciliation before importing into modern EHR or practice management systems.

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 Essential MD Software Suite objects map to Nutshell

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)

maps to

Nutshell

People

1:1
Fully supported

Essential 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)

maps to

Nutshell

Lead

1:many
Fully supported

Essential 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

maps to

Nutshell

Company

1:1
Fully supported

Essential 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

maps to

Nutshell

Deal

1:1
Fully supported

Essential 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

maps to

Nutshell

Pipeline

1:1
Fully supported

Essential 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

maps to

Nutshell

Stage (on Deal)

1:1
Fully supported

Stage 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)

maps to

Nutshell

Task

1:1
Fully supported

Essential 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

maps to

Nutshell

Note

1:1
Fully supported

Essential 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

maps to

Nutshell

Custom Fields (on Person/Company/Lead/Deal)

1:1
Fully supported

Essential 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

maps to

Nutshell

Owner (User lookup on all records)

1:1
Fully supported

Essential 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

maps to

Nutshell

Attachment (re-upload to Nutshell)

1:1
Fully supported

Essential 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

maps to

Nutshell

Source_System_ID__c (custom field)

1:1
Fully supported

Essential 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.

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.

Essential MD Software Suite logo

Essential MD Software Suite gotchas

High

Patient ID remapping risk at migration time

High

Encounter-to-billing linkage integrity

Medium

Custom field schema discovery requires manual enumeration

Medium

Document export format and size limits

Low

Insurance payer name inconsistency between exports and destination

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

  • Lead vs. People routing requires pre-migration status audit

    Essential MD stores all person records in a single object with a status field distinguishing active contacts from leads. Nutshell splits these into separate Lead and People objects with distinct list views and field sets. Before migration, we audit the Essential MD status distribution so contacts marked as converted or active route to Nutshell People while unconverted or prospect-status records route to Nutshell Leads. If the Essential MD status pick-list uses non-standard labels, value mapping must be defined before the migration run so records land in the correct object.

  • Custom fields require Nutshell schema setup before data lands

    Nutshell custom fields must be created on the target object (Person, Company, Lead, or Deal) before any data referencing them is imported. Essential MD custom fields have no automatic schema equivalent — a text field in Essential MD may need to map to a pick-list, number, or date field in Nutshell depending on the content. We deliver a custom-field creation plan as part of the discovery phase, specifying field name, Nutshell field type, and whether the field should be required. The Nutshell admin must create these fields before the migration window opens.

  • Pipeline stage value mapping is per-pipeline, not global

    Nutshell pipelines have stage names scoped to each individual pipeline. If Essential MD has multiple deal pipelines with overlapping stage names (e.g., 'Demo' appears in Pipeline A and Pipeline B with different meanings), we must create a value map for each pipeline separately in Nutshell. The Nutshell API exposes pipeline and stage data as separate objects (pipelineId + stageId on the Deal record), so cross-pipeline stage name conflicts are resolved by pipeline-specific mapping tables delivered in the migration plan.

  • Activity history volume can exceed Nutshell API rate limits

    Essential MD accounts with large activity histories (50,000+ tasks and notes) require careful pacing against Nutshell's API rate limits. We use paginated reads from Essential MD and batch inserts into Nutshell with exponential backoff. For accounts exceeding 100,000 activity records, we recommend migrating the most recent 24 months of activity in the initial run and providing a separate activity export for older records that your team can review and manually import using Nutshell's bulk-import CSV template.

  • Owner resolution by email match may leave records unassigned

    Nutshell assigns record ownership by linking to a user account via email. Essential MD owner records store owner names but may not have a matching email address for every record. We run a pre-migration owner audit that reports the count of Essential MD owner records with resolvable Nutshell user matches versus the count that will land in the fallback owner. Your team decides whether to invite unmatched owners to Nutshell before migration or accept the fallback assignment for their records.

Migration approach

Six steps for a successful Essential MD Software Suite to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Essential MD Software Suite logo

Essential MD Software Suite

Source

Strengths

  • Bundled scheduling, clinical documentation, and billing in a single platform reduces tool sprawl for small practices
  • On-premise deployment option provides direct data control for practices with strict data residency requirements
  • Specialty-specific workflow templates reduce initial configuration overhead for common practice types
  • Predictable bundled pricing covers core modules without per-encounter or per-transaction fees
  • Patient-encounter-billing linkage is maintained natively within the platform's data model

Weaknesses

  • Thin web presence and minimal public documentation make independent evaluation difficult for prospective buyers
  • Limited published API surface reduces options for automated data extraction and migration tooling
  • Small review sample on G2 (2 reviews) limits confidence in reliability claims
  • Fewer integrations with modern telehealth, patient portal, and clearinghouse tools compared to cloud-native competitors
  • Slower feature development velocity reported by users compared to newer medical SaaS 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. 2 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 Essential MD Software Suite and Nutshell.

  • Object compatibility

    B

    2 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

    Essential MD Software Suite: Not publicly documented.

  • Data volume sensitivity

    B

    Essential MD Software Suite doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Essential MD Software Suite 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 Essential MD Software Suite to Nutshell data migrations

Answers to the questions buyers ask most during Essential MD Software Suite to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Essential MD to Nutshell migrations complete in 24–72 hours of clock time for under 50,000 records. The longest step is custom-field creation in Nutshell, which requires your admin to create fields before data can land. Larger setups with 200,000+ records, multiple pipelines, or a large activity history extend to 5–10 days. Pipeline-stage mapping validation and owner-resolution coverage are the primary timeline factors that determine whether a migration lands at the fast or slow end of the range.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Essential MD Software Suite.
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