CRM migration

Migrate from Empire SUITE to Nutshell

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

Empire SUITE logo

Empire SUITE

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Empire SUITE and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Empire SUITE logo

Empire SUITE

What's pushing teams away

  • Steep learning curve for new staff, particularly around the interaction between time-tracking, billing, and security role configuration.
  • Custom field-based security can be difficult to audit and maintain, leading to access inconsistencies as the team grows.
  • Limited API documentation makes it hard to integrate Empire SUITE with modern analytics or document-management tools.
  • Deployment-specific customizations make switching vendors costly, as role and field configurations do not transfer easily.

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 Empire SUITE objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Empire 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

maps to

Nutshell

Company

1:1
Fully supported

Empire 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

maps to

Nutshell

Lead

1:1
Fully supported

Empire 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

maps to

Nutshell

Deal

1:1
Fully supported

Empire 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

maps to

Nutshell

Pipeline

1:1
Fully supported

Each 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

maps to

Nutshell

Stage

1:1
Fully supported

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

maps to

Nutshell

Activity

1:1
Fully supported

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

maps to

Nutshell

Custom Fields (Company)

1:1
Fully supported

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

maps to

Nutshell

Custom Fields (Person)

1:1
Fully supported

Person-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

maps to

Nutshell

User

1:1
Fully supported

Empire 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

maps to

Nutshell

File Attachments

1:1
Fully supported

Empire 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

maps to

Nutshell

Not Migratable

1:1
Fully supported

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

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.

Empire SUITE logo

Empire SUITE gotchas

High

Custom Field-based Security Permissions vary by deployment

Medium

Empire TIME module may have isolated data stores

High

No public API documentation found in research

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

  • Lifecycle and status fields require custom field migration with no native equivalent

    Empire Suite instances commonly store lifecycle stage, customer tier, or lead scoring values that have no direct equivalent in Nutshell's standard object schema. These migrate as custom fields on the Person or Lead object, created in Nutshell's settings before import. The risk is that custom fields created after initial migration can cause duplicate-record detection to miss previously migrated entries during a delta run—FlitStack AI stores the Empire Suite source ID on each record to prevent this.

  • Multi-pipeline setups require Nutshell Pro or above before migration can proceed

    Empire Suite pipelines map one-to-one to Nutshell pipelines. Nutshell's Foundation plan ($13/user/month) supports a single pipeline only. Teams with two or more active pipelines in Empire Suite must upgrade to Nutshell Pro ($42/user/month) or Enterprise ($79/user/month) before migration validates. FlitStack AI creates the pipeline and stage configuration during the pre-migration setup step, but the plan tier must be confirmed before data is ingested.

  • Workflow and automation rules cannot be exported and must be rebuilt manually

    Empire Suite workflow rules, automated assignment rules, and sequence triggers operate within Empire Suite's own automation engine and do not expose an export API. Nutshell's automation tools—triggers, automation rules, and email sequences on the Pro plan—must be rebuilt from scratch. FlitStack AI exports a structured JSON reference of Empire Suite workflow definitions to assist your Nutshell admin during the rebuild phase.

  • Empire Suite API authentication and rate limits affect migration pacing

    Empire Suite's API authentication model (basic auth or OAuth depending on edition) and per-minute rate limits determine how quickly FlitStack AI can extract records during the migration window. Teams with large record volumes may need to coordinate an API rate-limit increase or schedule migration during off-peak hours to avoid throttling the source system.

  • N:N contact-to-company associations collapse to a primary company link

    Empire Suite supports associating one contact with multiple companies. Nutshell's Person record links to one primary Company; additional company associations require manual re-creation after migration using Nutshell's Account Contact Relationships feature. We flag multi-company contacts during the mapping phase and surface them in the pre-migration report so your team can prioritize secondary associations.

Migration approach

Six steps for a successful Empire SUITE to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Empire SUITE logo

Empire SUITE

Source

Strengths

  • Integrated project-accounting, time-tracking, and billing within one suite.
  • Custom security roles with field-level permission granularity.
  • Designed for professional services and compliance-sensitive industries.

Weaknesses

  • API and integration capabilities are not well-documented publicly.
  • Custom fields and roles are deployment-specific, creating migration complexity.
  • Limited third-party ecosystem compared to major 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. 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 Empire 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

    Empire SUITE: Not publicly documented..

  • Data volume sensitivity

    B

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

Estimator

Estimate your Empire 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 Empire SUITE to Nutshell data migrations

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

Can't find your answer?

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 consultation

Most Empire Suite to Nutshell migrations complete in 48–72 hours of clock time for under 25,000 total records. Larger setups with 100,000+ records or multiple active pipelines extend to 5–7 days. The pre-migration schema setup phase—creating custom fields and configuring Nutshell pipelines—adds 2–3 days before data movement begins and is included in the project timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Empire 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