CRM migration
Field-level mapping, validation, and rollback between Empire SUITE and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Empire SUITE
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Empire SUITE and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Empire Suite stores CRM data across Contacts, Companies, Deals, Leads, Activities, and custom fields—typically with pipeline-stage and owner assignment metadata attached to each record. Nutshell organizes the same concepts into People, Company, Leads, Deals, and Activities, with a JSON-RPC API that supports full CRUD operations and export/import of custom field data. FlitStack AI extracts Empire Suite records via API, maps each field to its Nutshell counterpart, creates custom fields in Nutshell's Company/Person/Lead settings before import, and ingests via Nutshell's import API. Workflows, automations, and email sequences are not migratable—they require manual rebuild using Nutshell's automation tools or exported definitions as a reference. A sample migration with field-level diff runs first to validate mapping accuracy. The full run then executes with a 24–48 hour delta-pickup window capturing any records modified during cutover. Original create dates are preserved as custom metadata since Nutshell sets CreatedDate at import time.
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 Empire 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.
Empire SUITE
Contact / Person
Nutshell
Person
1:1Empire Suite contacts map directly to Nutshell People. The Person object in Nutshell stores name, email, phone, job title, address, and custom fields. Owner assignment resolves by email match against Nutshell users before migration runs.
Empire SUITE
Company / Account
Nutshell
Company
1:1Empire Suite companies map to Nutshell Company records 1:1. Company name, domain, industry, employee count, and annual revenue transfer directly. Parent-company hierarchies in Empire Suite map to the Parent Company field in Nutshell.
Empire SUITE
Lead
Nutshell
Lead
1:1Empire Suite leads map to Nutshell Leads with a value-mapping step on the status field. Empire Suite lead status values (e.g., New, Contacted, Qualified) map to Nutshell's status pick-list: New, Working, Dead, Qualified. Unmapped status values default to New.
Empire SUITE
Deal / Opportunity
Nutshell
Deal
1:1Empire Suite deals migrate to Nutshell Deals with name, amount, expected close date, stage, and owner intact. Deal amount is a currency field in Nutshell. If Empire Suite stores deal probability separately, it migrates as a custom field since Nutshell calculates stage-based probability automatically.
Empire SUITE
Pipeline
Nutshell
Pipeline
1:1Each Empire Suite pipeline maps to a Nutshell pipeline. Nutshell's Foundation plan supports one pipeline; Pro and above support up to five pipelines. We create Nutshell pipelines during the pre-migration setup phase and map stage names value-by-value.
Empire SUITE
Pipeline Stage
Nutshell
Stage
1:1Stage names in each Empire Suite pipeline map to Nutshell stage names in the corresponding pipeline. This mapping is pipeline-specific—one Empire Suite pipeline maps to one Nutshell pipeline with its own stage configuration. Stage order and probability are preserved as part of the pipeline definition.
Empire SUITE
Activity (Call / Email / Meeting / Note)
Nutshell
Activity
1:1Empire Suite call, email, meeting, and note records map to Nutshell Activities. Activity type, subject, body, date, and associated person or deal are preserved. Original activity timestamps transfer as the Activity Date in Nutshell.
Empire SUITE
Custom Fields (Company-level)
Nutshell
Custom Fields (Company)
1:1Empire Suite custom fields on Company objects require pre-creation of matching custom fields in Nutshell's Company settings before import. Field type mapping applies: text → String, number → Number, date → Date, pick-list → Choice. Custom field API names in Nutshell follow the configured field label format.
Empire SUITE
Custom Fields (Person/Contact-level)
Nutshell
Custom Fields (Person)
1:1Person-level custom fields from Empire Suite migrate to Nutshell Person custom fields. Nutshell's settings UI exposes these under Company Settings → Person Fields. Fields are created before the migration import step, and data populates during the import phase.
Empire SUITE
Owner / User
Nutshell
User
1:1Empire Suite owner IDs resolve by email against Nutshell user accounts. Unmatched owners are flagged before migration with a fallback owner assignment option. Nutshell user records are identified by their email address in the JSON-RPC authentication model.
Empire SUITE
Attachment / File
Nutshell
File Attachments
1:1Empire Suite file attachments on records are downloaded and re-uploaded to Nutshell as file attachments linked to the corresponding Person, Company, Lead, or Deal. File size limits apply per Nutshell's upload constraints.
Empire SUITE
Workflow / Automation
Nutshell
Not Migratable
1:1Empire Suite workflow rules, automated sequences, and trigger-based automations have no direct equivalent in Nutshell's automation model and cannot be exported. We provide a structured export of workflow definitions as a rebuild reference for your Nutshell admin.
| Empire SUITE | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Person | Person1:1 | Fully supported | |
| Company / Account | Company1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal / Opportunity | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Pipeline Stage | Stage1:1 | Fully supported | |
| Activity (Call / Email / Meeting / Note) | Activity1:1 | Fully supported | |
| Custom Fields (Company-level) | Custom Fields (Company)1:1 | Fully supported | |
| Custom Fields (Person/Contact-level) | Custom Fields (Person)1:1 | Fully supported | |
| Owner / User | User1:1 | Fully supported | |
| Attachment / File | File Attachments1:1 | Fully supported | |
| Workflow / Automation | Not Migratable1: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.
Empire SUITE gotchas
Custom Field-based Security Permissions vary by deployment
Empire TIME module may have isolated data stores
No public API documentation found in research
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 Empire Suite API and create Nutshell custom field schema
FlitStack AI connects to the Empire Suite API using your provided credentials to audit record counts, custom field definitions, and pipeline configurations. In parallel, we create all required custom fields in Nutshell under Company Settings, Person Fields, and Lead Fields to match Empire Suite's extended property schema. The pipeline and stage structure in Nutshell is configured to mirror Empire Suite's active pipelines. This step typically takes 2–3 days and produces a data map ready for review.
Resolve owner and user assignments by email
Empire Suite owner IDs are resolved against Nutshell user accounts by email address. FlitStack AI generates a pre-migration owner resolution report listing matched users and any unmatched owners. Unmatched owners require either a Nutshell user account to be created before migration or a fallback owner assignment. No data is migrated until the owner resolution report is confirmed, preventing records from landing without a Nutshell owner.
Run sample migration with field-level diff
A representative slice of records—typically 100–500 across People, Companies, Leads, Deals, and Activities—migrates first. FlitStack AI generates a field-level diff report comparing Empire Suite source values against the migrated Nutshell records. You verify stage mapping, custom field population, owner assignment, and date preservation. Mapping corrections are applied before the full run proceeds.
Execute full migration with delta-pickup window
The full Empire Suite dataset migrates into Nutshell via the JSON-RPC import API, sequenced to resolve foreign keys correctly (Companies first, then People, then Leads and Deals). A 24–48 hour delta-pickup window runs concurrently, capturing any records created or modified in Empire Suite during the migration execution. FlitStack AI's audit log records every operation, and one-click rollback is available if reconciliation detects a record count discrepancy exceeding the agreed tolerance threshold.
Deliver reconciliation report and rebuild reference package
Post-migration, FlitStack AI delivers a full reconciliation report showing record counts by object, any records skipped due to validation errors, and the delta-pickup log. The rebuild reference package includes the exported Empire Suite workflow definitions in structured JSON, a field-mapping summary, and a pipeline/stage comparison table to guide your Nutshell admin through rebuilding automations and sequences.
Platform deep dives
Empire 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 Empire 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
Empire SUITE: Not publicly documented..
Data volume sensitivity
Empire 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 Empire SUITE to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Empire 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 Empire 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.