CRM migration

Migrate from Intrix CRM to Nutshell

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

Intrix CRM logo

Intrix CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

60%

6 of 10

objects map 1:1 between Intrix CRM and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Intrix CRM to Nutshell is a shift from a vertically integrated SME platform that bundles project management and HRM into a single subscription to a focused sales CRM built for small and midsize teams. Intrix stores the relationship between Clients and Contacts as separate records; Nutshell uses Companies and People with an explicit link. We extract all Client and Contact records from Intrix's CSV exports, resolve the parent-Client relationship at migration time, and map it to the Company-to-Person link in Nutshell. Opportunities in Intrix map directly to Nutshell Deals with stage mapping against the customer's active pipeline configuration. Intrix Activities (calls, emails, meetings, tasks) migrate as Nutshell Activities with timestamps and owners preserved. Projects, Working Hours Records, and Support Tickets do not have native Nutshell equivalents and require manual rebuild or custom field configuration post-migration. Intrix has no public API, so every migration relies on manual CSV export from the Intrix UI, which adds planning time for accounts with more than 5,000 records.

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

Intrix CRM logo

Intrix CRM

What's pushing teams away

  • Limited third-party app marketplace creates integration gaps, especially with legacy ERP and accounting systems that mid-market teams rely on.
  • Lack of a public API documented for external migration tools makes automated export and import difficult and manual CSV-heavy.
  • Stale data accumulates when teams lack integration with email platforms and marketing tools they have already standardized on.
  • Smaller market presence and review volume compared to HubSpot or Pipedrive makes it harder to find peer feedback and specialist support.
  • Scale constraints emerge as teams grow custom fields and automation complexity beyond what the platform comfortably handles.

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

Each row shows how a Intrix CRM 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.

Intrix CRM

Client

maps to

Nutshell

Company

1:1
Fully supported

Intrix Client records map 1:1 to Nutshell Companies. Standard fields (company name, industry, address, phone, website) migrate directly. The Client ID is preserved as an external reference field so that the original Intrix record can be identified during reconciliation. Company is imported before any Person or Deal record to satisfy Nutshell's required link from People to Companies.

Intrix CRM

Contact

maps to

Nutshell

Person

1:1
Fully supported

Intrix Contact records map 1:1 to Nutshell People. Each Contact carries a reference to its parent Client; we resolve this to the Nutshell Company ID during import and set the Company link on every Person record. First name, last name, email, phone, title, and custom fields migrate as typed properties. Contacts without a valid parent Client are imported with a flag for manual Company assignment.

Intrix CRM

Opportunity

maps to

Nutshell

Deal

1:1
Fully supported

Intrix Opportunities map directly to Nutshell Deals. Deal name, value, expected close date, stage, owner, and custom fields migrate 1:1. Stage names from Intrix are customer-specific and require a stage mapping table that we extract from the customer's active pipeline configuration and apply to Nutshell's Deal stage values.

Intrix CRM

Pipeline Stages

maps to

Nutshell

Deal Stages

lossy
Mapping required

Intrix pipeline stages are customer-configurable with custom names and order. We extract the full stage definition per pipeline (stage name, position, probability if set) from the Intrix export and configure matching Deal Stages in Nutshell before any Deal records are imported. Stage probabilities round to Nutshell's supported integer format.

Intrix CRM

Activities (calls, emails, meetings, tasks)

maps to

Nutshell

Activities

1:1
Fully supported

Intrix Activities (calls, emails, meetings, tasks) logged against Clients, Contacts, or Opportunities migrate as Nutshell Activities. Each Activity carries the original timestamp, owner, and description. Calls and tasks from Intrix map to Nutshell Activity with the type field set appropriately. Emails and meetings migrate as notes-style Activities with the original content preserved in the description field since Nutshell does not store threaded email history in the same structure as Intrix.

Intrix CRM

Projects

maps to

Nutshell

None (no native equivalent)

lossy
Mapping required

Intrix Projects with task dependencies, deadline automation, and resource assignments have no native Nutshell equivalent. Nutshell is a sales CRM and does not include a project management module. We document every active Intrix Project as a written record with its tasks, dependencies, deadlines, and owners for the customer's admin to rebuild in their chosen project management tool post-migration.

Intrix CRM

Tasks

maps to

Nutshell

None (no native equivalent)

lossy
Mapping required

Intrix Tasks with project dependencies cannot be imported as-is into Nutshell because Nutshell Tasks do not support predecessor dependency logic. We extract the full task list per project, including dependency order and completion status, and deliver it as a structured CSV inventory. The customer's admin recreates tasks manually or in their project management tool.

Intrix CRM

Working Hours Records (WHR)

maps to

Nutshell

None (no native equivalent)

lossy
Mapping required

WHR data is only available on Intrix Advanced and Unlimited tiers. Nutshell has no native time-tracking module. We export WHR records as structured data and map them to a set of custom fields on Nutshell Person or Company records if the customer requires the data to remain in their CRM. Otherwise, we deliver a written WHR inventory with clock-in/clock-out timestamps, hours worked, and employee reference for manual entry or third-party time-tracking integration.

Intrix CRM

Custom Fields

maps to

Nutshell

Custom Properties

1:1
Mapping required

Intrix custom fields on Clients, Contacts, Opportunities, and Activities migrate to Nutshell custom properties on the corresponding object (Company, Person, Deal, Activity). We extract the full custom field schema per object, map field types to Nutshell's supported property types (text, number, date, dropdown, checkbox), and provision the custom properties in Nutshell before record import begins.

Intrix CRM

Attachments

maps to

Nutshell

Attachments

1:1
Not supported

Intrix stores file attachments per Client, Contact, or Project. We download attachments individually from the Intrix UI export and re-upload them to the corresponding Nutshell Company, Person, or Deal record. File-per-record structure means we handle each attachment separately during import, which adds time for accounts with more than 500 attachments.

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.

Intrix CRM logo

Intrix CRM gotchas

High

No public API for automated export or import

Medium

Tier-gated modules affect what data exists

Medium

Project task dependencies require ordered import

High

Trial data deletion after 30 days

Low

Limited integrations create data silos

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

  • No public API means manual CSV export only

    Intrix does not publish a REST API endpoint for automated data extraction. All migration work requires logging into the Intrix UI, navigating to each module (Clients, Contacts, Opportunities, Activities, Projects, Working Hours Records), and exporting each object as a separate CSV file. For accounts with more than 5,000 records, this manual process is time-intensive and prone to data entry errors in the export. Any re-sync after initial migration also requires manual re-export. We advise customers to allocate dedicated time during the export phase and to validate CSV completeness before handoff to migration import.

  • Project task dependencies cannot be preserved in Nutshell

    Intrix enforces task completion logic based on predecessor dependencies. A task cannot be marked complete if its dependency is open. Nutshell Tasks do not support predecessor dependency chains. We extract the full dependency graph and task order from Intrix, but we cannot reconstruct that logic in Nutshell. Any project with complex task dependencies must be documented and rebuilt in a dedicated project management tool post-migration. This is not a data loss issue — it is a capability gap between a vertically integrated CRM and a focused sales CRM.

  • Client-Contact parent-child relationship requires explicit link resolution

    Intrix stores Contacts as separate records linked to Clients by an internal ID. Nutshell Companies and People are linked by the Person's Company field, which must be set explicitly during import. If a Contact's parent Client has not yet been imported, the Person record will be created without a Company link and must be reconciled post-import. We sequence Company import before Person import to minimize this risk, but any Contact with a missing or renamed parent Client requires manual correction.

  • Working Hours Records have no Nutshell destination

    WHR data exists only on Intrix Advanced and Unlimited tiers. Nutshell does not include a time-tracking module. WHR records (employee, date, clock-in, clock-out, hours worked, project code if applicable) can be stored as custom fields on Nutshell Person or Company records, but this requires pre-provisioning the custom fields and accepting that time-tracking remains a manual or third-party-tool process post-migration. We confirm WHR existence and volume during scoping and advise on the custom field approach before migration begins.

  • Third-party integrations require manual reconfiguration after migration

    Intrix integrations (MailChimp, Google Calendar, accounting tools) store connection credentials and sync state that cannot be exported. After migration to Nutshell, the customer must manually reconnect each integration through Nutshell's integrations directory. Nutshell's 500+ integrations cover most common tools (Slack, QuickBooks, Xero, PandaDoc, Zapier), but any niche or custom integration requires evaluation for availability in Nutshell's marketplace. We deliver a written inventory of all active Intrix integrations for the customer to reconfigure post-migration.

Migration approach

Six steps for a successful Intrix CRM to Nutshell data migration

  1. Scoping and CSV export planning

    We audit the Intrix account to identify which modules are active (Basic vs Advanced vs Unlimited), confirm the volume of records per object (Clients, Contacts, Opportunities, Activities, Projects, WHR, Support Tickets if applicable), and document the active pipeline stage configuration. We provide the customer with a step-by-step export checklist for each Intrix module so that CSVs are ready before migration begins. If the account is on a trial plan, we flag the 30-day data deletion risk and advise completing the export before the window closes.

  2. CSV delivery review and data quality assessment

    The customer delivers Intrix CSV exports to us. We run a data quality assessment: duplicate detection on Contact email addresses, missing required fields (name, email on Person records), invalid date formats, and orphaned records (Contacts without a parent Client). We produce a data quality report and a field mapping table that pairs each Intrix CSV column header to the corresponding Nutshell field. The customer approves the mapping before any import begins.

  3. Nutshell custom field provisioning

    We provision all required custom properties in Nutshell (Company, Person, Deal, Activity custom fields from the mapping table) before any record import. This includes setting property types (text, number, date, dropdown, checkbox), defining dropdown option lists, and ensuring field-level visibility is set to writable for the migration user. Custom properties for WHR data are created here if the customer has chosen to store time records as CRM custom fields.

  4. Company and Person import with relationship resolution

    We import Intrix Clients as Nutshell Companies first, preserving the original Intrix Client ID as an external reference field. We then import Intrix Contacts as Nutshell People, resolving each Contact's parent Client ID to the corresponding Nutshell Company ID and setting the Person's Company field explicitly. Any Person records with unresolved parent Clients are flagged in a reconciliation report for the customer to resolve manually. Email deduplication runs at this stage.

  5. Deal and Activity import

    We import Intrix Opportunities as Nutshell Deals, applying the stage mapping table to set Deal stage values. Owner assignment resolves by matching Intrix Owner email to Nutshell User email. Activities (calls, emails, meetings, tasks) import last with timestamps and owner assignment preserved, linked to the corresponding Company and Person records. Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, delta sync, and integration handoff

    We freeze writes to Intrix during the cutover window, run a delta sync of any records modified during migration, and confirm all record counts in Nutshell match the source exports. We deliver a written inventory of all active Intrix integrations (MailChimp, Google Calendar, accounting tools), active Projects and task dependencies, and any WHR data that requires a third-party time-tracking tool. We do not rebuild Intrix Workflows, HRM automations, or Support Tickets in Nutshell; those are separate configuration work outside migration scope.

Platform deep dives

Context on both ends of the pair

Intrix CRM logo

Intrix CRM

Source

Strengths

  • Tiered pricing from €27/user/month with no per-contact billing adds predictability for growing sales teams.
  • Combines CRM, project management, and HRM in one platform reducing tool sprawl for SMEs.
  • Mobile app with business card scanner and electronic signing keeps field teams productive offline and online.
  • Free minor customization adjustments during use lowers the cost of iterative configuration changes.
  • Working Hours Records module provides compliant time tracking for EU-based teams with attendance requirements.

Weaknesses

  • No publicly documented API endpoint means all migration work depends on manual CSV export and re-import.
  • Limited third-party integrations compared to HubSpot or Pipedrive restricts connectivity with existing tool stacks.
  • Support module and WHR are add-on costs on top of base tier pricing, inflating the real per-user cost.
  • Small review sample on G2 and GetApp makes it difficult to assess long-term user satisfaction and common pain points.
  • Project dependencies are powerful but complex to migrate — incorrect sequencing breaks task completion logic in the new system.
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 Intrix CRM 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

    Intrix CRM: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between two and four weeks for accounts under 3,000 total records with no Working Hours Records or complex project data. Migrations above 3,000 records or involving Advanced/Unlimited tier data (WHR, Support Tickets, projects with task dependencies) extend to five to eight weeks because each module requires a separate CSV export, custom field provisioning, and manual rebuild documentation for data with no native Nutshell destination.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Intrix CRM.
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