CRM migration

Migrate from Inception to Nutshell

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

Inception logo

Inception

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Inception and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Inception logo

Inception

What's pushing teams away

  • External commercial database review creates data latency — changes approved by third-party providers do not appear in the live CRM immediately.
  • Limited integrations with smaller pharmaceutical wholesalers — customers report gaps connecting to niche distributors and smaller partners.
  • Platform scoped narrowly to pharma rep workflows — teams needing broader CRM capabilities outgrow it once they diversify beyond field sales.

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

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)

maps to

Nutshell

People

1:1
Fully supported

Inception 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

maps to

Nutshell

Company

1:1
Fully supported

Inception 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

maps to

Nutshell

Lead

1:1
Fully supported

Inception 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

maps to

Nutshell

Deal

1:1
Fully supported

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

maps to

Nutshell

Activity

1:1
Fully supported

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

maps to

Nutshell

Custom Field on People

1:1
Fully supported

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

maps to

Nutshell

Custom Field on Company

1:1
Fully supported

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

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

Inception 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

maps to

Nutshell

Custom Field on Deal / Tag

1:1
Fully supported

Inception 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

maps to

Nutshell

Custom Object / Custom Field

1:1
Fully supported

Inception 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

maps to

Nutshell

File Attachment

1:1
Fully supported

Inception 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

maps to

Nutshell

User (matched by email)

1:1
Fully supported

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

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.

Inception logo

Inception gotchas

Medium

External database sync delays record visibility

Medium

Visit outcome codes vary by implementation

High

Analytics exports are definition-only, not data

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

  • Pharma-specific custom objects have no Nutshell equivalent and must be stored as reference data

    Inception CRM stores pharma-specific data — HCP relationship records, sample lot tracking, and dispensing logs — that Nutshell cannot natively model. When we migrate these records, we extract the field values and store them as a JSON payload in a Nutshell custom field on the related Person or Deal record. Your team retains access to the historical data but cannot use Nutshell's native features to interact with it. Before migration, we recommend deciding whether this reference data should be exported to a separate system or archived as a compliance record.

  • Inception territory assignments require manual rebuild as Nutshell does not have a native territory object

    Inception's territory model lets you assign deals or users to geographic or product-based territories with inheritance rules. Nutshell has no native territory object — territory data in Inception maps to a custom text field on the Deal record that we create before migration. Your Nutshell admin will need to decide how to act on this data: either build Nutshell workflow rules that reference the territory value, create Nutshell Teams mapped to territories, or use the field for reporting segmentation only. We flag the mapping decision during discovery.

  • Inception workflow and automation logic does not transfer to Nutshell

    Inception workflows governing deal stage transitions, lead assignment rules, and follow-up task generation are built within Inception's automation engine and have no export format. Nutshell's automation model uses different triggers (pipeline stage changes, form submissions, time-based) and cannot import Inception rule definitions. We provide a workflow audit export listing every active Inception workflow with its trigger, conditions, and actions so your Nutshell admin can rebuild them in Nutshell's automation settings.

  • Custom field type mismatches may require field type conversion during migration

    Inception custom fields support types (multi-select pick-list, currency with precision, date-time) that Nutshell's custom field system may represent differently. Nutshell custom fields on People, Companies, and Leads support text, number, date, and pick-list. When a mismatch occurs, we preserve the raw value as a text field and flag it in the migration report. Your team reviews the flagged fields post-migration and can reconfigure field types in Nutshell settings if needed — Nutshell allows changing field types for custom fields without deleting existing data.

  • Inception API rate limits may extend migration duration for large datasets

    Inception's API operates within rate limits determined by your plan tier and platform usage. For migrations exceeding 25,000 records, API pagination and throttling can extend the extraction phase beyond the initial estimate. We monitor API response codes during extraction and apply exponential backoff when 429 errors occur. Large migrations include a pre-migration API audit step that estimates extraction time based on your current rate limit status and record volume. We also log all throttling events for later analysis.

Migration approach

Six steps for a successful Inception to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Inception logo

Inception

Source

Strengths

  • Purpose-built for pharmaceutical rep workflows including visit tracking and HCP targeting.
  • Streamlined interface that field sales teams adopt quickly without extensive training.
  • Strong daily KPI tracking against individual plans and targets.
  • Competitive pricing relative to enterprise pharma platforms like Veeva.
  • Good customer service responsiveness according to verified reviews.

Weaknesses

  • External commercial database integrations introduce variable latency on record updates.
  • Narrower integration ecosystem compared to larger CRM platforms — gaps with smaller pharmaceutical distributors.
  • Analytics exports limited — reporting definitions must be manually rebuilt on destination platforms.
  • Platform focused on field sales; less suited for teams with complex non-pharma CRM needs.
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. 1 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 Inception and Nutshell.

  • Object compatibility

    B

    1 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

    Inception: Not publicly documented..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Inception to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Inception-to-Nutshell migrations complete in 48–72 hours of clock time for datasets under 25,000 records. The longest phase is typically the pre-migration audit and custom field mapping plan, which runs 3–5 business days depending on how many custom fields and pharma-specific objects need mapping decisions from your team. Datasets exceeding 25,000 records or containing extensive activity history extend the full migration to 5–7 days.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Inception.
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