CRM migration
Field-level mapping, validation, and rollback between EXACT and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
EXACT
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between EXACT and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Exact and Nutshell both model the core CRM objects — accounts, contacts, leads, opportunities, and activities — but they diverge on relationship cardinality and custom-field architecture. Exact stores contacts and companies with one-to-many linkages and exposes custom fields through its ERP-adjacent schema; Nutshell uses a unified people/company model with per-record-type custom fields for companies, people, and leads. The migration carries all standard objects, custom fields, activity history (calls, emails, meetings, notes), and file attachments into Nutshell's equivalent structures. Workflows, sequences, automation rules, reports, and third-party integrations do not migrate — FlitStack exports those definitions as JSON for your Nutshell admin to rebuild using Nutshell's automation engine and native reporting. The migration runs via Nutshell's JSON-RPC API over HTTPS with scoped read access on Exact; your team continues working in Exact throughout the cutover window. During the migration, data loads in dependency order to maintain referential integrity, with companies migrated first to establish primary keys that contacts, leads, and opportunities reference. A delta pickup window captures any records modified during the cutover period, ensuring Nutshell reflects Exact's final state at go-live.
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 EXACT 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.
EXACT
Account
Nutshell
Company
1:1Exact Accounts map directly to Nutshell Companies. Nutshell's Company object holds name, domain, industry, employee count, annual revenue, and address fields. Parent-child company hierarchies in Exact map to Nutshell's parent Company field. The parent company must be migrated before child companies to maintain the hierarchy relationship correctly.
EXACT
Contact
Nutshell
Person
1:1Exact Contacts map to Nutshell People. The Person object in Nutshell stores first name, last name, email, phone, job title, and address. Each Person can be linked to a primary Company record via the AccountId equivalent. The Company must be migrated first to establish the link.
EXACT
Lead
Nutshell
Lead
1:1Exact Leads migrate as Nutshell Leads — a separate record type in Nutshell that tracks status, source, and owner. Leads in both systems have a lifecycle from New through Qualified to Converted. Custom lead status values require manual mapping in Nutshell before migration validation.
EXACT
Opportunity
Nutshell
Target
1:1Exact Opportunities map to Nutshell Targets. Both represent deal records with a name, amount, stage, close date, and owner. Nutshell Targets are tied to a Company and optionally a Person record. The Company link must exist before Targets are loaded.
EXACT
Pipeline / Pipeline Stage
Nutshell
Pipeline / Stage
1:1Nutshell Pipelines use the same stage model as Exact but stage pick-list values are account-wide. Stage names map value-by-value; probability and forecast category re-applied from Nutshell side after migration. Unmapped stages require manual setup in Nutshell before the full run.
EXACT
Activity (Call / Email / Meeting)
Nutshell
Activity
1:1Exact activities (calls, emails, meetings) map to Nutshell Activities with original timestamps, owners, and subject preserved. The activity type maps to Nutshell's Activity type field. Activity links to records are updated post-load using the ID mapping table.
EXACT
Note
Nutshell
Note
1:1Exact notes migrate as Nutshell notes attached to the relevant Company, Person, Lead, or Target record. Rich-text formatting is preserved where possible. Each note requires a valid relatedId pointing to the migrated record.
EXACT
Attachment / File
Nutshell
File
1:1Exact file attachments are downloaded and re-uploaded to Nutshell Files using Nutshell's file API. Each file is relinked to its source record by ID mapping. Files over 25MB are flagged before migration for admin decision on handling.
EXACT
Custom Field (per object)
Nutshell
Custom Field (per tab)
1:1Exact custom fields map to Nutshell custom fields on the equivalent tab (Company, Person, or Lead). Each custom field requires creation in Nutshell before migration, with type mapping from Exact's data type to Nutshell's field type options. A creation manifest is provided to the admin.
EXACT
User / Owner
Nutshell
User
1:1Exact users are resolved by email match against Nutshell users. Unmatched owners are flagged before migration; your team either invites them to Nutshell first or assigns records to a fallback owner. No record migrates without a valid Nutshell owner to prevent orphaned records.
EXACT
Lead Status
Nutshell
Lead Status
1:1Lead status pick-list values map value-by-value from Exact to Nutshell. Custom statuses require manual value mapping setup in Nutshell before migration validation runs. Unmapped statuses are flagged in the pre-migration diff report.
EXACT
Task
Nutshell
Task
1:1Exact tasks migrate to Nutshell tasks with subject, due date, status, and owner preserved. Task dependencies do not exist in Nutshell and are dropped during migration. Tasks without valid owners are assigned to the fallback owner.
| EXACT | Nutshell | Compatibility | |
|---|---|---|---|
| Account | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Opportunity | Target1:1 | Fully supported | |
| Pipeline / Pipeline Stage | Pipeline / Stage1:1 | Fully supported | |
| Activity (Call / Email / Meeting) | Activity1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Attachment / File | File1:1 | Fully supported | |
| Custom Field (per object) | Custom Field (per tab)1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Lead Status | Lead Status1:1 | Fully supported | |
| Task | Task1: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.
EXACT gotchas
Strict API rate limits gate bulk extraction
Exact Globe vs Exact Online feature drift
Workflow and signalling rules are not exportable
OAuth token lifecycle requires careful handling
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
Generate Exact data export and Nutshell schema audit
FlitStack pulls a full data export from Exact covering Accounts, Contacts, Leads, Opportunities, Activities, Notes, and Attachments via Exact's API or export tools. Simultaneously, we audit your Nutshell account to inventory existing custom fields, pipeline configurations, and user list. The combined output drives the field mapping manifest and flags any Nutshell-side pre-creation required before data loads. This parallel approach ensures both systems are assessed before field mapping begins.
Create Nutshell custom fields from Exact schema
Based on the field mapping manifest, FlitStack generates a step-by-step custom field creation plan for Nutshell: field name, data type (text, number, date, pick-list), and target tab (Company, Person, Lead). Your Nutshell admin creates these fields before the migration run. We validate the Nutshell schema API confirms each field exists before we proceed to data loading, preventing validation failures during the migration run.
Resolve owners and users by email
Nutshell user accounts are matched against Exact owner records by email. Unmatched owners are flagged with the Exact owner name and email so your team can either invite them to Nutshell or assign their records to a fallback user. No record migrates without a valid Nutshell owner; this prevents orphaned records in Nutshell after migration and ensures accountability is maintained for all migrated data.
Run a sample migration with field-level diff
A representative slice — typically 100–500 records spanning Accounts, Contacts, Leads, Opportunities, and Activities — migrates first. FlitStack generates a field-level diff report comparing Exact source values against Nutshell destination values for each mapped field. You review the diff to verify custom field mapping, status value mapping, and owner resolution before the full run commits, catching any mapping issues early.
Execute full migration with delta-pickup window
The full migration loads in dependency order: Companies first (foreign key for Contacts and Leads), then Persons and Leads, then Targets with stage and owner mapping, then Activities with ID link updates, then Notes and Files. A delta-pickup window (24–48 hours) captures any Exact records modified during the cutover. FlitStack generates an audit log of every record operation and runs a reconciliation count against Exact's pre-migration totals.
Deliver reconciliation report and rollback plan
Post-migration, FlitStack delivers a reconciliation report showing record counts by object, any records that failed to load, and the reasons for each failure. A one-click rollback script is available if reconciliation reveals critical gaps. The ID mapping table is included in the delivery package so your admin can trace any Nutshell record back to its Exact source for audit purposes.
Platform deep dives
EXACT
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 EXACT and Nutshell.
Object compatibility
1 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
EXACT: 60 API calls per minute AND 5,000 API calls per day, per app per company. Signalled via X-RateLimit-Minutely-Remaining/Reset and X-RateLimit-Daily-Remaining/Reset headers. HTTP 429 returned on overrun..
Data volume sensitivity
EXACT exposes a bulk API — large-volume migrations stream efficiently.
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 EXACT to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your EXACT 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 EXACT
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.
