CRM migration
Field-level mapping, validation, and rollback between Inception and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Inception
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Inception and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Inception CRM is built around pharmaceutical sales workflows — territory management, sample tracking, and HCP (healthcare professional) relationship data that has no direct equivalent in standard SMB CRMs. Nutshell uses a conventional object model: People (contacts), Companies, Leads, and Deals, with custom fields available per object. We map Inception's standard contact, company, and deal records directly into Nutshell's equivalent objects. Inception's custom fields and any pharma-specific properties migrate as Nutshell custom fields, though the underlying meaning may need your team to validate against Nutshell's field types. We cannot migrate Inception workflows, territory assignments, or sample-lot tracking logic — those are destination-side configuration decisions. Our migration engine connects to Inception's API, extracts all People, Companies, Deals, and Activities, applies the field mapping, and loads into Nutshell via their API. A 24-48 hour delta window captures any records modified during the cutover window. The migration process also preserves original create timestamps and owner assignments, ensuring that each Nutshell record retains its historical context. We log every API call and maintain a detailed audit trail for compliance review. If any field type mismatch occurs, we flag the record and store the raw value as text for post‑migration validation.
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 Inception 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.
Inception
Person (Contact)
Nutshell
People
1:1Inception Person records map directly to Nutshell People. Nutshell People store contact fields (name, email, phone, address) and link to a Company record. We map all standard fields and attach the People record to its mapped Company. During migration, we preserve the original created date and owner information, ensuring a complete history in Nutshell.
Inception
Company
Nutshell
Company
1:1Inception Company records map 1:1 to Nutshell Company records. Company name, domain, industry, employee count, and revenue fields migrate directly. Parent-company hierarchies in Inception map to Nutshell's parent-company relationship field. We also transfer the company's primary contact information and any associated custom fields to maintain full context.
Inception
Lead
Nutshell
Lead
1:1Inception Lead records migrate to Nutshell Leads with status and source fields preserved. Leads without a converted status in Inception land as Nutshell Leads; leads already converted to Person map to Nutshell People with a flag indicating prior conversion. This ensures accurate lead routing and historical tracking in Nutshell.
Inception
Deal
Nutshell
Deal
1:1Inception Deal records map to Nutshell Deals with deal name, amount, stage, and close date transferred. The Inception pipeline stages map to Nutshell pipeline stages — we apply a stage-value mapping table built from your Inception stage configuration during the discovery phase.
Inception
Activity (Call, Email, Meeting, Note)
Nutshell
Activity
1:1Inception calls and emails map to Nutshell Activities with type, subject, date, duration, and linked record preserved. Meetings map to Nutshell Activities with start/end time and attendees. Notes migrate as Nutshell note entries attached to the relevant Person, Company, or Deal.
Inception
Custom Field (Person-level)
Nutshell
Custom Field on People
1:1Inception custom fields on Person records that have no direct Nutshell equivalent are created as Nutshell custom fields on People before migration. We preserve the field label, data type, and pick-list values from Inception and recreate them in Nutshell settings.
Inception
Custom Field (Company-level)
Nutshell
Custom Field on Company
1:1Inception Company custom fields migrate as Nutshell Company custom fields. If a custom field in Inception stores a value type (e.g., multi-select pick-list) that Nutshell does not support natively, we store the value as a text custom field and flag it for your team to review post-migration.
Inception
Custom Field (Deal-level)
Nutshell
Custom Field on Deal
1:1Inception Deal custom fields migrate as Nutshell Deal custom fields. We capture the field type from Inception and recreate it in Nutshell. For Inception fields that store numeric identifiers (e.g., sample lot IDs), we preserve them as text fields since Nutshell Deal custom fields do not have a dedicated ID type.
Inception
Territory Assignment
Nutshell
Custom Field on Deal / Tag
1:1Inception territory assignments are stored per deal or per user and have no direct Nutshell equivalent. We preserve the territory value as a custom text field on the Deal record so your team can use it for reporting or to drive Nutshell workflow rules.
Inception
Sample Tracking Record
Nutshell
Custom Object / Custom Field
1:1Inception sample tracking records (lot numbers, HCP dispensing records, compliance logs) have no Nutshell equivalent. We extract these records and store them as a JSON payload in a Nutshell custom field on the associated Deal or Person, preserving the data for reference even though Nutshell cannot process it natively.
Inception
Attachment / File
Nutshell
File Attachment
1:1Inception file attachments on People, Companies, or Deals are extracted and re-uploaded to Nutshell as file attachments linked to the target record. File size limits apply per Nutshell's upload constraints. We flag any file exceeding Nutshell's limit for manual handling.
Inception
Owner / User
Nutshell
User (matched by email)
1:1Inception owner IDs resolve to Nutshell users by email address match. Unmatched owners are flagged before migration — your team can either invite them to Nutshell first or reassign their records to a designated fallback user. No record lands without a valid Nutshell owner.
| Inception | Nutshell | Compatibility | |
|---|---|---|---|
| Person (Contact) | People1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Activity (Call, Email, Meeting, Note) | Activity1:1 | Fully supported | |
| Custom Field (Person-level) | Custom Field on People1:1 | Fully supported | |
| Custom Field (Company-level) | Custom Field on Company1:1 | Fully supported | |
| Custom Field (Deal-level) | Custom Field on Deal1:1 | Fully supported | |
| Territory Assignment | Custom Field on Deal / Tag1:1 | Fully supported | |
| Sample Tracking Record | Custom Object / Custom Field1:1 | Fully supported | |
| Attachment / File | File Attachment1:1 | Fully supported | |
| Owner / User | User (matched by email)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.
Inception gotchas
External database sync delays record visibility
Visit outcome codes vary by implementation
Analytics exports are definition-only, not data
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 Inception data model and build custom field mapping plan
We connect to your Inception account via API and extract a full schema snapshot: all object types, custom field definitions, pick-list values, and relationship metadata. We compare this against Nutshell's available field types and create a custom field creation plan for any Inception field that has no direct Nutshell equivalent. This step produces a field mapping spreadsheet your team reviews before we touch any data.
Create Nutshell custom fields and validate pipeline configuration
Before migrating records, we create all required custom fields in Nutshell using the mapping plan from Step 1. We also validate your Nutshell pipeline configuration — confirming that pipeline stages match the stage-value mapping table derived from Inception. Any missing stages or mismatched pick-list values are flagged for your Nutshell admin to resolve before we proceed to data migration to ensure accurate record mapping.
Resolve owner records and validate user mapping
We extract all Inception owner IDs and cross-reference them against Nutshell users by email address. Owners without a corresponding Nutshell account are listed in a pre-migration report with a recommended fallback assignment (a designated Nutshell admin or the system default owner). No records are migrated until all owner mappings are resolved — this prevents orphan records with unresolvable owner references.
Run sample migration with field-level validation
A representative slice of 100–500 records — spanning People, Companies, Leads, Deals, and Activities — migrates into Nutshell under a test configuration. We generate a field-level diff report comparing source values against destination values for every mapped field. Your team reviews the diff, confirms that custom field values landed correctly, and validates that linked records (Company on People, Deal on Activities) resolved properly. We iterate on the mapping until the diff passes your sign-off.
Execute full migration with delta-pickup window
The full record set migrates into your live Nutshell account. A delta-pickup window of 24–48 hours runs after the initial bulk load, capturing any Inception records modified during the cutover period. All operations are logged in our audit trail. If reconciliation identifies missing or mismatched records, one-click rollback reverts the Nutshell state to pre-migration and we re-run the affected object types.
Platform deep dives
Inception
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 Inception 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
Inception: Not publicly documented..
Data volume sensitivity
Inception 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 Inception to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Inception 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 Inception
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.