CRM migration

Migrate from Attio to Nutshell

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

Attio logo

Attio

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between Attio and Nutshell.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Attio to Nutshell is a schema simplification, not a straight record copy. Attio's flexible object-relational model lets teams define any business entity as a custom object; Nutshell uses a fixed schema built around Contacts, Accounts, and Deals with optional custom fields. We audit every Attio object during scoping, map custom objects to custom fields on Nutshell's standard records, and resolve relationship chains (which Attio's CSV export flattens) using the API to prevent Deals from arriving orphaned from their Companies. Attio Lists do not migrate directly; we extract list membership criteria and document the equivalent Nutshell Smart List filter logic for the admin to rebuild. Workflows and credit-consuming automations are inventoried but not migrated, since Nutshell's automation model differs fundamentally from Attio's action-block credit structure. Activity history (calls, emails, meetings, notes) transfers as timeline entries on the matching Contact, Account, or Deal record.

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

Attio logo

Attio

What's pushing teams away

  • The data model flexibility requires significant upfront configuration time, and sales teams without technical resources struggle to build a useful workspace from scratch.
  • Reporting features lack depth—users cite weak pipeline analytics, missing date-based segmentation, and limited data visualization as ongoing frustrations.
  • Native integrations are limited; syncing with tools like Aircall and HubSpot requires workarounds or third-party sync platforms, breaking GTM stack cohesion.
  • The workspace credit model creates unpredictable monthly costs—AI enrichment and automation steps consume credits faster than teams anticipate on Plus plans.
  • Teams cite a steep learning curve where the flexibility that attracts technical founders becomes a burden for adoption across sales, marketing, and CS teams.

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

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

Attio

People

maps to

Nutshell

Contact

1:1
Fully supported

Attio People records map directly to Nutshell Contacts. Standard Attio fields (name, email, phone, job title, website) map to their Nutshell equivalents. Custom attribute fields on the Attio People object map to Nutshell custom fields on Contact, subject to the destination plan's custom field limit (20 on Standard, 50 on Pro, 100 on Power). Email addresses serve as the dedupe key during import to prevent duplicate Contacts. Relationship links to Companies are resolved against the Accounts created in the preceding import phase.

Attio

Companies

maps to

Nutshell

Account

1:1
Fully supported

Attio Company records map to Nutshell Accounts. The Attio company domain populates the Account website field, and the company name becomes Account.name. Nutshell Accounts support a many-to-many relationship with Contacts through the Account's linked Contact records. We resolve this relationship after both objects are created so that the Contact-to-Account link is satisfied at import time rather than requiring a second pass.

Attio

Deals

maps to

Nutshell

Deal

1:1
Fully supported

Attio Deals map to Nutshell Deals. Attio's pipeline stages map to Nutshell Deal status values, and Attio's deal amount maps to Nutshell's value field. We validate that the destination Nutshell plan supports Deal objects (available on Standard and above). Relationship attributes linking Deals to their parent Company (Account) and associated People (Contacts) are resolved using the Account ID and Contact IDs created in earlier import phases, preventing Deals from arriving without an Account association.

Attio

Custom Objects

maps to

Nutshell

Custom Fields on standard objects

lossy
Mapping required

Attio custom objects (Gated 3 on Free, 5 on Plus, 12 on Pro, unlimited on Enterprise) have no direct Nutshell equivalent because Nutshell does not support custom objects on any tier. We audit each custom object during scoping, map its attributes to custom fields on the closest Nutshell standard object (Contact, Account, or Deal), and consolidate related attributes into field groups. If the total custom field count exceeds the destination plan's limit, we recommend upgrading Nutshell or reducing the field set before migration.

Attio

Notes

maps to

Nutshell

Note

1:1
Fully supported

Attio Notes are first-class API objects attached to any record. They migrate as Nutshell Notes linked via ContentDocumentLink to the parent Contact, Account, or Deal. Note timestamps and author attribution are preserved. Rich text formatting in Attio Notes is converted to plain text for Nutshell compatibility, with a flag in the migration report for any notes with unsupported formatting that require manual review.

Attio

Activities (Emails, Calls, Meetings, Tasks)

maps to

Nutshell

Activities on Contact, Account, or Deal

1:1
Fully supported

Attio engagement records (email, call, meeting, task) map to Nutshell Activity records attached to the appropriate Contact, Account, or Deal. We resolve the parent record ID (Contact or Account) at migration time by querying the email address or company domain to match against the already-migrated Contact and Account records. Activity timestamps are preserved to maintain the timeline order that sales reps rely on for deal context.

Attio

Lists

maps to

Nutshell

Smart Lists (documented for manual rebuild)

lossy
Mapping required

Attio Lists are dynamic filtered collections of records defined by attribute conditions, not standalone records. Nutshell does not have a native equivalent to Attio's dynamic Lists. We extract each List's filter criteria (attribute conditions, relationship filters, sort order) and document them as a step-by-step Smart List rebuild guide for the Nutshell admin. List membership counts are preserved in a migration report so the admin can validate the rebuilt Smart Lists against the original counts.

Attio

Owner

maps to

Nutshell

Owner

1:1
Fully supported

Attio User records and Owner assignments on records map to Nutshell Owner references. We match by email address. Any Attio Owner without a matching Nutshell user is held in a reconciliation queue for the customer to provision before record import resumes, since OwnerId is a required reference on Deals and optional on Contacts and Accounts.

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.

Attio logo

Attio gotchas

High

CSV exports flatten relationship chains

Medium

Credit consumption burns budget faster than seat price suggests

Medium

Custom objects gated by plan tier during migration

Low

Email sync only for People and Company records

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

  • Attio CSV exports flatten relationship chains

    Attio's workspace export produces flat CSV files per object. Relationship attributes (which Company a Deal belongs to, which People are linked to a Deal, which Contacts are related to an Account) do not export as join keys. We resolve this by querying the Attio API to pull the full relationship graph before writing to Nutshell. Without API-based relationship resolution, Deals arrive orphaned from their Account and Contact associations in Nutshell, breaking pipeline reporting and activity timelines that depend on those links.

  • Nutshell has no custom objects

    Attio's core differentiator is its flexible relational object model, which allows teams to define custom objects for entities like Subscriptions, Investors, or Projects. Nutshell does not support custom objects on any plan tier. We consolidate Attio custom objects into custom fields on Nutshell's standard Contact, Account, and Deal objects during scoping. If the total custom field count exceeds the destination plan's limit, we flag this before migration begins and recommend either a plan upgrade or field consolidation. Custom object relationship attributes (cross-object links) cannot be preserved as foreign keys in Nutshell and are documented for manual re-entry.

  • Attio Lists have no Nutshell equivalent

    Attio Lists are workflow-context collections of records filtered by attribute conditions, stored as dynamic server-side queries. Nutshell does not have dynamic lists; it has static groups and a manual Smart List builder. We extract the filter criteria for every Attio List during scoping and deliver a written Smart List rebuild guide with the equivalent Nutshell conditions. List membership counts are reconciled post-migration against the rebuilt Smart Lists, but the list definitions themselves require manual recreation in Nutshell.

  • Custom field limits vary by Nutshell plan

    Nutshell's custom field limits are plan-gated: 20 on Standard, 50 on Pro, 100 on Power and Enterprise. Attio's custom attributes per object have no equivalent plan cap on Pro and Enterprise. We audit the total custom attribute count across all Attio objects during scoping and compare it to the destination plan's limit. If the migration would exceed the limit, we recommend upgrading the Nutshell plan or consolidating attributes into multi-value fields before migration begins.

  • Workflows and automation sequences do not migrate

    Attio Workflows consume workspace credits per action block and are gated by plan tier. Attio Sequences are sales engagement cadences available on Pro and Enterprise. Nutshell's automation model is more limited, using basic workflow rules rather than Attio's block-based automation builder. We do not migrate Workflows or Sequences as automation logic. We deliver a written inventory of every active Attio Workflow and Sequence with its trigger, conditions, actions, and a recommendation for the equivalent Nutshell setup. The customer's admin rebuilds these in Nutshell post-migration.

Migration approach

Six steps for a successful Attio to Nutshell data migration

  1. Discovery and scoping audit

    We audit the source Attio workspace across plan tier, object count, custom object definitions, attribute types, relationship attributes, active Lists, active Workflows, and engagement volume. We compare the Attio object and field inventory against the destination Nutshell plan's custom field limits and standard object availability. The discovery output is a written migration scope with a complete Attio-to-Nutshell object and field map, a flag list for any custom objects requiring consolidation, a relationship graph extract from the Attio API, and a Nutshell plan upgrade recommendation if the destination plan cannot accommodate the migrated field count.

  2. Relationship graph extraction and schema design

    We query the Attio API to extract the full relationship graph for every object: which Contacts belong to which Accounts, which Deals are linked to which Accounts and Contacts, and which Notes and Activities attach to which records. We then design the Nutshell schema, creating the custom fields on Contact, Account, and Deal that correspond to Attio's custom object attributes. We configure the Nutshell Deal pipeline with stage values mapped from Attio's deal stages. The schema is deployed into a Nutshell trial or sandbox org for validation before any data is migrated.

  3. Sandbox migration and reconciliation

    We run a full migration into the Nutshell validation environment using production-like data volume. The customer reconciles record counts (Contacts in, Accounts in, Deals in, Activities in), spot-checks 20-30 random records against the Attio source, and reviews the relationship chain completeness report. Any field mapping corrections, custom field additions, or relationship resolution gaps are resolved here. The customer signs off the sandbox migration before the production cutover date is confirmed.

  4. Owner and user reconciliation

    We extract every distinct Attio Owner referenced on People, Companies, Deals, Notes, and Activities and match by email against the Nutshell destination's user list. Owners without a matching Nutshell user go to a reconciliation queue for the customer to provision before migration resumes. Owner assignments are required on Deals and optional on Contacts and Accounts, so this step gates the Deal import phase.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Attio Companies), Contacts (with AccountId resolved and relationship links restored), Deals (with AccountId and associated ContactIds resolved from the relationship graph), Activities (Tasks, Emails, Calls, Meetings attached to the correct Contact or Account by email-domain match), Notes (linked via ContentDocumentLink to the parent record). Custom object attributes are written as custom fields during the Contact and Deal import phases. Each phase emits a row-count reconciliation report. Attio writes are frozen during the cutover window.

  6. Cutover, final delta, and Workflow handoff

    We run a final delta migration of any Attio records modified during the cutover window, then enable Nutshell as the system of record. We deliver the List rebuild guide, the Workflow and Sequence inventory document, and the Attio relationship chain report for the customer's admin to review. We support a five-business-day hypercare window for reconciliation issues. Workflow and Sequence rebuild in Nutshell, List recreation, and admin training are outside the migration scope and are handled as separate engagements.

Platform deep dives

Context on both ends of the pair

Attio logo

Attio

Source

Strengths

  • Flexible object schema allows modeling any business entity, not just contacts and deals.
  • Permanent free tier with 50k records and 3 users for evaluation without a countdown timer.
  • Automatic email and calendar sync builds interaction history without manual data entry.
  • Workspace export to CSV covers all objects for backup and migration scoping.
  • Clean API-first architecture with webhooks and OAuth 2.0 for developer integrations.

Weaknesses

  • Reporting and analytics lack depth compared to established CRM platforms.
  • Integration library is thin—native connections to common GTM tools are limited or missing.
  • Credit consumption model makes monthly costs unpredictable for automation-heavy teams.
  • Learning curve is steep for non-technical users who expect a pre-built CRM experience.
  • Feature gates push growing teams to Pro ($69/user/mo) sooner than expected.
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 Attio 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

    Attio: 100 requests/sec for reads, 25 requests/sec for writes; sliding window algorithm with 10-second window. 429 responses include a Retry-After header.

  • Data volume sensitivity

    A

    Attio exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

Walk through your Attio 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 three and five weeks for workspaces under 15,000 People, 3,000 Deals, and no custom objects. Migrations with multiple custom objects, complex relationship attribute chains, large engagement histories (over 200,000 activity records), or plan-upgrade-dependent Nutshell destinations move to six to ten weeks because of relationship graph extraction, custom object consolidation, and sandbox validation scope.

Adjacent paths

Related migrations to explore

Ready when you are

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