Skip to content
Get a quote

Migrate to Nutshell

Nutshell is a sales-focused CRM whose import model rewards teams that pre-build pipelines, respect the People/Companies/Leads/Accounts split, and resolve plan-tier custom-field caps before the first CSV row is uploaded.

Short answer

FlitStack AI migrates pipelines, contacts, and deals into Nutshell from 850+ CRMs. Every field is mapped to Nutshell's objects, history and associations come across, the Nutshell setup is configured alongside, and the whole migration stays reversible in one click.

By

From Your system
DestinationNutshell
850+ sources mapped into Nutshell

What Nutshell supports, and where its import tools stop

  • 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.
Bulk APIHTTP Basic auth: username = company domain or email, password = API key. OAuth user-impersonation supported for specific integrations (e.g., Zapier).
Rate limitsNot publicly documented in summary form.
ObjectSupportNote
PeoplefullPeople records are the core contact object in Nutshell, holding name, email, phone, address, and standard fields. We extract all standard fields via API and map them directly to Contacts or Leads in destination CRMs. Custom fields per Person are supported and mapped 1:1.
CompaniesfullCompanies represent organizations and serve as the parent record for People in Nutshell's flat hierarchy. We map Company records to Accounts in destination CRMs, preserving the company-level custom fields and any associated People links.
LeadsmappedLeads in Nutshell are distinct records separate from People, with their own custom fields and lifecycle. We merge Leads into Contacts or map them to a separate Leads object depending on destination capabilities, preserving Lead source and status as custom Contact properties.
ActivitiesfullActivities capture calls, emails, meetings, and tasks tied to People or Companies. We extract the full activity timeline per record and recreate it as Activities or Engagements in the destination, maintaining the date, type, and notes.
PipelinesfullNutshell supports multiple pipelines, each with configurable stages. We extract pipeline definitions including stage names, order, and win/loss status, then recreate them in the destination CRM using the equivalent pipeline configuration interface.
Pipeline StagesmappedStage-level data including probability, stage order, and stage-specific automation triggers are extracted. We map these to destination stage definitions but note that probability percentages and automation triggers may require manual reconfiguration post-migration.
Custom FieldsfullCustom fields can be created for Companies, People, and Leads via Settings. We enumerate all custom field definitions across objects before migration and create matching custom fields in the destination CRM, preserving field type and option lists.
AttachmentsnoneThe Nutshell API exposes attachment metadata and references but does not return binary file blobs directly. We export attachment filenames and URLs but cannot automatically download and re-upload files. Customers must manually re-attach files post-migration or use a separate file transfer method.
TagsmappedNutshell uses a tag-based taxonomy for categorizing People and Companies. Tags are exported and mapped to Tags or Labels in destination CRMs, but tag hierarchy (if any) is flattened during transfer.
Users/OwnersmappedUsers in Nutshell serve as record owners and appear in activity logs. We map Nutshell users to Owner or User records in the destination CRM. Users without email access in the destination may be mapped as historical owners rather than active seats.
Email SequencesnoneEmail sequences are stored as automation configurations on the Pro and Business plans. These are not exportable via API. We do not migrate sequences—we migrate the People and their activity history so follow-up can be restarted in the destination CRM.
Nutshell IQ (Enrichment)noneNutshell IQ provides contact and company data enrichment via a credit-based system. Enrichment data is not separately stored as a migrateable field—it is displayed inline in the Nutshell UI. We do not attempt to transfer IQ enrichment data.

The Nutshell migration guide

Why teams migrate to Nutshell

The four shapes a Nutshell migration takes, and what makes the platform easier — or harder — than the category average.

Nutshell is a sales-focused CRM built by Nutshell Inc. for small and mid-sized B2B teams that want a working pipeline, email sequences and reporting without a Salesforce-style admin function1. The product is a Sales Suite with five plan tiers — Foundation, Growth, Pro, Business and Enterprise — plus add-ons like Power AI and the Nutshell IQ prospecting bundle28.

The typical Nutshell customer is a 5 to 100-seat sales organisation — agencies, manufacturers, professional services and SMB SaaS — that wants pipeline visibility wired to email sync without paying Salesforce-tier economics. Compared with HubSpot Sales Hub, Nutshell positions on flatter pricing; compared with Pipedrive, on richer email marketing and AI summarisation; compared with Zoho CRM, on cleaner UX.

The shapes of migration that actually land on Nutshell tend to fall into four patterns. First, spreadsheet exits — teams that have outgrown Google Sheets pipelines and want a CRM with contact merge, email logging and pipeline reporting. Second, Salesforce or HubSpot downgrades, driven by total cost of ownership on teams that never used Apex, Flows or marketing automation heavily.

Third, legacy replacements — Act!, Insightly, Capsule, Highrise, SugarCRM or homegrown databases — where the source schema is loose and the project is really a re-architecture. Fourth, M&A consolidation, where an acquired business runs on a different CRM and the parent standardises on Nutshell. A Pipedrive migration has clean object parity; a Salesforce migration carries rich automation that does not move across at all.

What makes migrating to Nutshell easier than the category average is the import tool itself — it accepts CSV files, runs through a mapping wizard with field-level previews, and ships an Import2-powered direct-from-CRM path for sources including Salesforce, HubSpot, Pipedrive and Zoho2278. Custom fields are addressable on every paid plan.

What makes it harder than the average is the four-object record model — People, Companies, Leads and Accounts — which forces a split that Pipedrive and HubSpot users do not have to think about. Custom-field counts are also plan-tier gated, which catches mid-market teams off guard when they discover the cap in the middle of mapping.

Pipelines, stages, email sequences, lead scoring rules and reports do not import — they are rebuilt from documentation. Teams that scope for the rebuild up front finish on time; teams that assume parity do not.

Teams that scope for the rebuild work up front finish on time; teams that assume parity do not.

The Nutshell data model you need to map into

Objects, custom fields, pipelines, and the match keys you'll wire on every record — the destination schema decoded.

Nutshell's CRM is built around four core record types — People, Companies, Leads and Accounts — surrounded by activities, notes, tasks and pipelines. The split between Leads (open opportunities) and Accounts (closed-won customers) is the most important shape to internalise before any field mapping starts.

Before you can map a field, you need to know which destination object the row belongs on, what fields it requires, and which value serves as its match key. The table below summarises the objects you will touch in a Nutshell migration.

ObjectWhat it storesRequiredTier
PeopleIndividual contacts — leads, prospects, customersFirst name or last name; email recommendedAll plans
CompaniesOrganisations associated with people and leadsCompany nameAll plans
LeadsOpen sales opportunities in a pipeline with Confidence + ValuePrimary person or company, pipeline, stageAll plans
AccountsClosed-won customers (post-sale relationship)Name, associated companyPro and above
Activities (calls, meetings, logged emails, tasks)Engagement timeline eventsType, timestamp, owner, associated person/company/leadAll plans
NotesFree-text annotations on People, Companies or LeadsBody, parent recordAll plans
ProductsCatalogue of sellable items linked to Leads via line-item-like attachmentName, unit pricePro and above
Sources, Markets, Industries, CompetitorsReference lists used to tag People, Companies and LeadsNameAll plans
TagsLightweight free-form labels on recordsTag valueAll plans

People are matched by exact name first, then email address on import — if neither matches, a new contact is created150. Companies use company name as the match key. Leads have no natural unique key, so either let Nutshell assign Lead IDs and store them back, or carry the source platform's deal ID in a custom Text field on the lead.

Once a record is created, its Nutshell ID is the canonical primary key for any update path — re-importing the same CSV without a stable external ID column creates duplicates that have to be merged manually after the fact78. Plan for this on day one.

When you import via the CSV wizard, Nutshell creates new records by default and offers a deduplication step for matches. Custom-field types determine validation; the catalogue below covers what you can model and the per-plan limits to plan around.

Field typeLimitNotes
Text (single line)225 characters maxStores any alphanumeric string59
Long TextParagraph-scale, larger than 225 charsUsed for descriptions, notes-like fields59
CurrencyNumeric with monetary displayRespects the account's default currency setting
DateDate-only; no time componentStored without timezone offset
EmailStandard email format validationLowercased; available on People, Companies and Leads
DecisionMultiple-choice picklist — Yes/No or custom optionsClosest analogue to a single-select dropdown59
AddressStructured street/city/state/zip/countryMultiple address slots per record
Phone, URLString-typed with format hintMultiple phone slots per People record
Product (Leads only)Reference to entries in the Products catalogueLets a lead carry value tied to specific products59
Custom fields per objectPlan-tier gated — Foundation has tighter caps than BusinessVerify your exact cap in Settings → Custom Fields before mapping114

Relationships are modelled as associations between People, Companies and Leads — a Lead can carry multiple People (decision maker, influencer, end user) and one primary Company. Accounts associate to Companies and the People who work there. There is no formal junction object; the platform leans on tags, custom fields and the Lead-Person link table to express many-to-many.

Pipelines are first-class — every Lead lives in exactly one pipeline with one stage. Multiple pipelines per account are supported on paid plans, and each pipeline carries its own Stage list, Confidence percentages and automation. Stages do not cascade, so the same logical stage name may need to be created on every pipeline you build156.

Pre-migration prep — the work before you touch Nutshell

What must be true on the source, the destination, and across the team before the first row hits the import wizard.

The single best predictor of a clean Nutshell migration is how much work you do on the source side before the first import button is pressed. Nutshell's own best-practice guide is explicit that file setup decides whether records land correctly — encoding, column separation and field formatting are the fix, not post-import cleanup41.

The single best predictor of a clean migration is how much work you do before the first import button is pressed.

Treat the source export as raw material that needs shaping to Nutshell's expected formats — saved as UTF-8 CSV, each piece in its own column, phone numbers normalised, dates rewritten to a consistent format, Decision values matched to the picklist created in Nutshell, owners resolved to existing user accounts41.

Source-side prep

  • Audit and dedup the source database before export — Nutshell merges People on exact name first and email second, so duplicates that share neither land as separate records and have to be merged in the UI one at a time150.
  • Normalise emails to lowercase, trim whitespace, and strip role-based addresses (info@, sales@). Casing differences are not always caught by the matcher.
  • Stamp a stable external ID on every record — a UUID or the source platform's primary key — and map it into a custom Text field per object so re-runs are deterministic.
  • Decide what is in scope for historical activities. Calls, meetings, tasks and logged emails can be imported with an activity date stamp, but Products can only be imported alongside Leads113.
  • Save the file as UTF-8 — Nutshell's importer rejects other encodings with an error page immediately after upload, before any mapping happens79.

Destination-side prep

  • Trial a sandbox account by starting Nutshell's 14-day free trial in a separate workspace and dry-running the import end-to-end before you load production. Nutshell ships no formal sandbox on lower tiers, so the trial workspace is the practical stand-in.
  • Provision users first and confirm their email addresses match the source export's Owner column exactly — Nutshell maps owners by email, and rows whose owner email is missing land unowned.
  • Pre-create every custom field on the right object with the right type — Text vs Long Text vs Decision matters, and changing a field's type after creation usually means recreating it.
  • Build every pipeline and stage before importing Leads — Leads targeting a non-existent stage are rejected or land in the pipeline's default stage rather than where you intended156.
  • Decide your default lead owner and assignment rules before kicking off the import — automatic lead distribution can fight with importer behaviour if both are active.

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every department that touches the CRM. Train sales reps on Activity logging, Lead Confidence updates and pipeline drag-and-drop before go-live, not after. A small-business migration runs one to two business days; a complex multi-pipeline Nutshell migration runs two to four weeks of elapsed time. Build the human runway accordingly.

Import mechanisms: CSV wizard and Import2

Two paths in, each with different ergonomics and trade-offs. Picking the wrong one is how mid-migrations stall at scale.

Nutshell exposes two main load paths and the right one depends on dataset size and source platform. The native CSV Import wizard covers one-shot migrations under a few tens of thousands of records. The Import2-powered direct-CRM tool handles common SaaS sources end-to-end.

Native CSV Import wizard

The CSV importer lives under Setup → Import (or Settings → Data → Import on newer accounts) and walks through file upload, object selection, column mapping, and a preview step before commit22141. Three object types are supported: Companies, People and Leads. The wizard tracks past imports under an Import History list at the bottom of the same page75.

File requirements: CSV format with UTF-8 encoding, each field in its own column, header row drives mapping4179. Public documentation does not specify a hard row cap, but practitioners chunk files at 5,000–10,000 rows per upload to keep mapping responsive. Products can only be imported attached to Leads — there is no standalone product importer113.

Import2 direct-CRM migration

For migrations from other CRMs, Nutshell partners with Import2 to offer one-click migration from sources including Salesforce, HubSpot, Pipedrive, Zoho CRM, Insightly, Highrise, Capsule CRM, Copper, SugarCRM and Act!141. The flow starts a free sample of up to 100 random Accounts plus their People, Leads and activities so you can verify mapping before committing.

Salesforce migrations have a dedicated path: Nutshell directly accepts the .zip file from Salesforce's Setup → Data Export tool78. Some Salesforce plans cap exports at once per month, so plan the export window against the cutover date.

Mapping your data into Nutshell

The longest section — because field mapping is where almost every migration that fails actually breaks.

Mapping is where every migration earns its scars. The schema decisions in your mapping spreadsheet determine whether reports work on day two, whether pipeline drag-and-drop fires the right automation on day five, and whether your sales team trusts the data on day thirty.

Work in import order: Companies first (so People and Leads can associate), then People, then Leads, then Activities and Notes, then Accounts and Products if you are on a plan that includes them.

People

Common source → Nutshell People mapping
SourceDestinationNote
emailEmail (primary)Lowercased on import; secondary match key after exact name150
first_name / last_nameFirst name / Last namePrimary match key — exact name match takes precedence over email150
phonePhone (multiple slots)Normalise to a consistent format; type tags (mobile, work) preserved
owner / account_ownerPerson owner (Nutsheller)Map by user email; pre-provision users or owner falls back to importing user
title / job_titleTitleSingle-line text, no length-driven validation beyond 225 chars
source / lead_sourceSources tagMap to the Sources reference list pre-built under Settings
created_atCapture in a custom Date fieldCreated date is system-managed and cannot be overwritten on standard import
tagsTagsSemicolon or comma-delimited on import depending on CSV settings

Companies

Common source → Nutshell Company mapping
SourceDestinationNote
company_nameNameRequired; primary match key for Companies
website / domainURLNot used as a match key by default — Name is the matcher
industryIndustryMap to the Industries reference list; create missing values pre-import
annual_revenueCustom Currency fieldNot a standard Company field — create as a custom Currency field
parent accountParent company associationSet via Account hierarchy on Pro+; on Foundation, capture in a custom Text field
market segmentMarketsMarkets is a built-in reference list separate from Industries

Leads and pipelines

Recreate every pipeline and stage in Nutshell before importing Leads. Each stage carries a Confidence percentage that drives forecast math — Initial Contact might be 10%, Qualified 40%, Proposal 70%, Closed Won 100%. Build the mapping table source-stage → Nutshell-pipeline + stage-name. Leads targeting a non-existent stage are rejected or land in the pipeline's default stage156.

If you are consolidating multiple source pipelines, keep them as separate Nutshell pipelines for at least 90 days post-migration, then merge once reporting has stabilised. Each pipeline carries its own stages — they do not cascade — so the same name ("Qualified") may need to be created on every pipeline.

Common source → Nutshell Lead mapping
SourceDestinationNote
deal_name / opportunity_nameLead name (description)Required; defaults to a generated label if blank
stage / pipeline_stageStage (within a Pipeline)Match exact stage name on the named pipeline156
amountValueCurrency; respects account default currency
probabilityConfidenceSet by stage by default; override per lead if source carried a manual value
close_dateExpected close dateDate-only; no timezone component
ownerLead assigneeMap by user email; lead owner controls forecast attribution
primary_contactPrimary person on LeadMatch by Person name + email; create the Person first to avoid mismatches
account / organisationCompany on LeadMatch by Company name; create the Company first

Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one. Migrate only fields used by an active process or report in the last 12 months. Excess fields weaken governance, eat into the plan-tier custom-field budget, and make Power AI's timeline summarisation less effective.

For Decision (picklist) fields whose source values do not match the destination, either: (1) extend the Nutshell Decision field with the missing options before import, (2) collapse adjacent values during transform, or (3) hold the legacy value verbatim in a parallel custom Text field. Source calculation properties do not import — Nutshell has no formula custom field, so precompute formula values during transform and drop them into a static Number, Currency or Text field.

Historical activities — emails, calls, meetings, notes, tasks

Nutshell supports importing activities with their original timestamps via the activity date field — this determines where each engagement lands on the People/Company/Lead timeline. Activity types map to Calls, Meetings, Logged Emails and Tasks; custom Activity Types can be created in Settings before import to mirror the source74.

Emails logged through Nutshell's email sync (Gmail/Outlook) appear on the timeline once a user connects their mailbox — but that path is post-cutover. For pre-cutover historical emails, export them from the source as a CSV of subject/body/timestamp/contact-email rows and load them as Logged Email activities through the importer. Rich HTML is accepted but plain-text often renders cleaner.

Power AI on the Pro plan adds timeline summarisation that distils long activity histories into AI overviews on demand. The feature reads whatever activities exist in Nutshell — so importing historical activities compounds in value on a Power AI plan. Zoom transcripts can also be summarised post-import via the Zoom integration.

Files and attachments

Attachments do not flow through the CSV importer. The supported path is to attach files manually in the UI after import. Public documentation does not publish a per-file size cap; practitioners report that very large files sometimes fail through the UI uploader and are best stored in S3 or Google Drive with a deep link in a custom URL field.

For large attachment estates (hundreds of GB), the pattern most teams adopt is: keep originals in external object storage, store a deep link in a custom URL field on the Nutshell record, and only inline-upload the most-referenced subset.

Audit trail, ownership and original timestamps

Nutshell-managed system fields — record created date, modified date, internal IDs — cannot be overwritten during CSV import. To preserve the original audit trail, create two custom fields per object — Legacy Created Date (Date) and Legacy Created By (Text) — and populate them from the source export.

Owner assignment during import works only if the owner email matches a provisioned Nutsheller at the moment of import; rows whose owner cannot be resolved fall back to the importing user as owner, which silently breaks downstream territory-based reports until corrected.

Account-wide change auditing is available via the Audit Log feature, but only on the Enterprise plan130. Lower plans can see Import History under Setup → Import to confirm which imports landed, but not per-field change history. Plan for this if compliance reporting is a hard requirement.

CRM-specific: lead scoring, email sequences, email/calendar sync

Lead-scoring models do not import — Nutshell uses Confidence percentages tied to pipeline stages plus optional per-lead overrides. To preserve historical lead scores, put them in a Legacy Lead Score custom Number field and let Confidence accrue forward from import day.

Email sequences (Nutshell's drip cadence tool) do not have an import mechanism — recreate the structure manually in Settings → Sequences and re-enroll active prospects post-cutover. Sequences are tied to People records, so People must land before sequences are turned on.

Email and calendar sync (Gmail/Outlook) is set up per user under Settings → Sync email after users are provisioned149158. Do not enable it during the import window or you will get a flood of duplicate timeline entries as the connector backfills. Nutshell's block list under Settings → Email security keeps HR, payroll and legal threads out of the synced timeline158.

The pitfalls that derail Nutshell migrations

Nine specific failure modes — ranked by impact, each tied to the exact Nutshell mechanism that breaks.

Validation and cutover

What to verify after the import job, in what order — and how to fail safely when something is wrong.

Validation is the bridge between the import finishing and users being allowed in. The most reliable signal is having department reps verify their own records — they know what right looks like better than any script. Run a three-stage protocol: a 10 percent test load with stakeholder spot-checks, the full load with real-time record-count monitoring, and a 30-day post-migration data-quality audit.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before users get login access.

  • Total People imported vs source — minus deliberately excluded rows (role-based emails, bounced lists, unsubscribed).
  • Total Companies imported vs source — checking that name-based merge did not over-collapse orgs with similar names.
  • Total Leads per pipeline per stage vs source, plus sum of Value per pipeline — a non-trivial dollar variance signals a stage-mapping error or currency-precision drop.
  • Total activities per type (Calls, Meetings, Logged Emails, Tasks) vs source — plus a date-bucketed comparison to confirm activity date round-tripped74.
  • Lead → Person and Lead → Company associations — count primary contacts and primary companies on Leads against source-derived expected counts.
  • Owner distribution — group by Lead owner and confirm no record landed unowned or assigned to the importing admin by mistake.
  • Match-key integrity — count distinct People by name and Companies by name; unexpected merges indicate the matcher caught name overlaps you didn't expect150.

On top of reconciliation, run a manual spot-check protocol: pick 30 random records across People, Companies and Leads and verify each field against the source UI. Pick five high-value Leads and trace the full association graph — primary Person, Company, products, recent Activities. If discrepancies show in three or more of the 30, halt the load, fix the root cause, and re-import the affected rows.

Nutshell ships no native bulk-undo for imports. The closest fallback is Import History under Setup → Import, which lists every import job, type, runner and timestamp75. From there you can identify the records added by a specific import and bulk-delete via the People/Companies/Leads list pages.

The real rollback strategy remains: export everything to S3 before the import starts, stamp every imported row with an Import Batch ID custom Text field, and if catastrophe strikes, filter by that batch ID, bulk-delete in the UI, and re-import from the cleaned source.

Cutover sequencing: (1) source goes read-only and the team is notified; (2) final delta export captures everything that changed during the test-import window; (3) delta is imported; (4) reconciliation runs; (5) users get login access and a 48-hour hyper-care window with the migration lead on call; (6) source decommission is scheduled for 30 to 90 days out, never the same day.

Migration partners and tools

Direct-CRM tools, iPaaS vendors, specialist migration shops — what each is good for and how to choose.

Nutshell's migration ecosystem centres on a small number of dedicated CRM-migration vendors plus the usual ETL/iPaaS connector landscape. The Import2 partnership is the closest thing to an official path — surfaced inside the Nutshell UI under Settings → Data → Import → Another CRM and supporting Salesforce, HubSpot, Pipedrive, Zoho, Insightly, Copper and Capsule141.

Other specialist vendors include Import2 (the embedded option), ClonePartner (engineer-led custom migrations with fixed-price quotes) and category platforms with Nutshell connectors. Each offers fixed-scope packages, sample migrations of around 100 records to validate mapping before commit, and post-migration support windows.

On the ETL and iPaaS side, Fivetran, Airbyte, Stitch, Workato and Zapier all have some level of Nutshell connector coverage121. Their role is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that converts Decision-field values, and the ongoing-sync layer after cutover.

Airbyte and Fivetran are common picks for warehouse-first teams; Workato is common where the migration is bundled with workflow automation rebuilds; Zapier handles the long tail of low-volume SaaS-to-Nutshell connections.

Managed-migration cost ranges vary widely. A clean Pipedrive-to-Nutshell move of under 25,000 records with no historical activities often lands in the $500–$3,000 range; ClonePartner publishes that 95% of their migrations cost less than $3,000. A Salesforce-to-Nutshell project with custom fields, historical activities and multiple pipelines typically runs $3,000–$15,000, with the upper end driven by record count, custom-field complexity and historical-activity depth.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Nutshell migrations and handles the field mapping, historical-data preservation, Decision-field option-list conversion, and validation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on record count and source platform, with separate line items for historical activity depth and the number of pipelines so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want the embedded Import2 flow, an iPaaS-first approach, or a specialist migration vendor. [Explore FlitStack →](/contact)

Nutshell migration checklist

An atomic, phased task list for migrating sales data into Nutshell — covering scope, prep, export, transform, sandbox test, cutover, validation, and post-cutover cleanup. Typical timeline: 4–12 weeks.

0. Decide & Plan10 tasks
  • Document the full list of Nutshell objects in scope. Nutshell exposes People, Companies, Leads, Activities, Notes, Tasks, Products, Sources, Markets, Industries, and Competitors as top-level objects. Confirm which are in scope and which are deliberately out of scope.If skipped: Discovering at cutover that Products or reference lists were assumed but never planned forces re-scoping mid-migration.
  • Define historical-data scope by object. Decide how many years of closed Leads, completed Activities, archived Notes, and synced email threads you will move. Email and call history is the largest single contributor to dataset size.If skipped: Pulling all history by default can multiply the dataset 5–10x and blow through the cutover window.
  • Confirm the target Nutshell plan and its feature gates. Nutshell offers Foundation, Growth, Pro, Power AI, and Enterprise tiers. Pipeline count, custom field allocation, sandbox availability, and Audit Log are gated by tier. Confirm the plan covers every feature on the migration's critical path.If skipped: Buying Foundation then discovering the migration needs Audit Log or extra pipelines blocks cutover until billing is escalated.
  • Decide whether Power AI features (timeline summarisation, Zoom transcription) are in scope. Power AI is a tier add-on. Confirm whether it needs to be configured at cutover or deferred to the 30-day follow-up.
  • Identify GDPR data-residency and retention requirements. Confirm which region your Nutshell tenant is provisioned in and that it satisfies any contractual residency commitments before any production data leaves the source.If skipped: Discovering after cutover that the tenant is in the wrong region forces a second migration or a contractual exception.
  • Confirm whether Audit Log (Enterprise-only) is required for compliance evidence. Account-wide Audit Log is gated to the Enterprise plan. If auditors require login history, bulk-edit tracking, or export tracking, the plan choice must reflect that.If skipped: Selecting a lower tier and then needing forensic audit evidence after cutover means scrambling for compensating controls.
  • Assign a single accountable migration owner (DRI). One named person owns scope decisions, cutover go/no-go, and post-migration signoff. Document their backup.
  • Document explicit out-of-scope items. List source-system features that will NOT be rebuilt in Nutshell — chat transcripts, marketing automation flows, custom reporting macros, etc. Get sponsor sign-off in writing.If skipped: Unwritten out-of-scope items resurface as urgent during cutover and derail the schedule.
  • Set the target cutover date and source-system freeze window. Pick a low-activity window (often a Friday evening through Sunday). Communicate the freeze date and time to all source-system users at least two weeks in advance.
  • Define written success criteria for the migration. Examples: 100% of open Leads migrated to correct Pipeline and Stage; aggregate Lead value within 0.5% of source; all Nutshellers assigned correctly; Activities linked to correct People, Companies, and Leads.If skipped: Without falsifiable criteria, the migration is never formally complete and tail issues drag on for months.
1. Pre-Migration Prep26 tasks
  • Run dedup analysis on source People using email as the primary match key. Resolve duplicate contacts at the source before export. Nutshell's duplicate matcher checks exact name first, then email — clean source data produces cleaner results.If skipped: Importing duplicates means rebuilding Lead-to-Person associations against the wrong record after merge.
  • Run dedup analysis on source Companies using domain as the match key. Normalize company-name variations (Acme Inc., Acme Incorporated, ACME) to a single canonical form before export.
  • Standardize email casing to lowercase across all People records. Mixed-case email values can create silent duplicates against the case-normalized keys Nutshell uses for fallback matching.
  • Normalize phone-number formats to E.164 with country code. Agree on one format (+15551234567) and apply it before export so the Phone custom-field type renders consistently.
  • Identify and resolve source records missing values that map to required Nutshell fields. Person name, Company name, and Lead title are mandatory in Nutshell. Records missing these will fail the CSV import wizard and land in an error report.If skipped: Mandatory-field misses produce error rows at import; without a triage plan you lose visibility into what failed.
  • Export baseline record counts per object as of the export timestamp. Capture counts for People, Companies, Leads, Activities, Notes, Tasks, Products, Sources, Markets, and Industries. These become the reconciliation target.If skipped: Without a baseline you cannot tell at validation whether 'missing' records were never exported or lost in transit.
  • Snapshot source pipeline definitions: pipeline name, stages, stage order, confidence percentages. Document every pipeline and every stage with its target confidence percentage. Nutshell supports multiple pipelines per sales process; capture the count.
  • Decide which closed-lost Leads are worth migrating. Closed-lost Leads from beyond your retention horizon may not justify the load time. Document the cutoff date.
  • Audit source attachment volume and per-record file size distribution. Capture total bytes, file count, and the largest file. This drives the attachment strategy in Phase 3c.
  • Provision the Nutshell production tenant on the chosen plan. Confirm Nutsheller count, currency, fiscal year, and default timezone at company creation.
  • Confirm sandbox availability on the chosen plan. Sandbox is not available on lower Nutshell tiers. If sandbox testing is required, verify the tier before Phase 4 begins; otherwise plan sandbox testing on a separate trial tenant.If skipped: Skipping sandbox forces all test errors to occur in production where rollback is harder.
  • Create every Nutsheller (user) account before any record import. Lead, Activity, Note, and Task owners match by Nutsheller email at import. Missing users default to the import-running Nutsheller, scrambling ownership.If skipped: If Nutshellers do not exist before import, every record is owned by one person and you must reassign tens of thousands of records manually.
  • Configure global account currency. Lead values and Currency custom fields render against the company currency. Set this before any Lead is loaded.
  • Set the company timezone to match the source system's timezone. Activity due dates and Lead close dates render against the company timezone; a mismatch silently shifts dates by hours.
  • Create every Pipeline and Stage that source Leads will land in. Match stage names exactly to what the transform spreadsheet will emit. Set each stage's confidence percentage (0–100) to match source intent before any Lead is loaded.If skipped: Importing Leads into a missing Stage assigns them to the default Stage and corrupts pipeline reporting.
  • Create all custom fields on People, Companies, and Leads before any import. Nutshell offers Text, Long Text, Currency, Date, Email, Decision (multi-choice), Address, Phone, URL, and Product custom-field types. Custom-field allocation per object varies by plan.If skipped: Importing into a custom field that does not exist drops the data silently. There is no retry after the import completes.
  • Define every Decision custom-field's full option list before import. Decision is Nutshell's multi-choice type (e.g. Yes/No, or an enumerated list). Every option referenced in source data must exist on the destination before that row arrives.If skipped: Decision values that do not exist in the destination list silently fail to populate the field.
  • Populate Sources, Markets, and Industries reference lists in advance. Source attribution, Market segmentation, and Industry classification are reference lists at the company level. Every value referenced by an imported Lead or Company must already exist.If skipped: Missing reference values are silently dropped from the imported record with no field-level error.
  • Configure the Products catalog before importing Leads that reference products. Nutshell Products attach to Leads via the Product custom-field type. Products cannot be imported separately without creating new Leads — load the catalog through the dedicated Product Importer first.If skipped: Leads imported before the Product catalog land with empty Product fields and require a second pass.
  • Configure Activity types in Settings to cover every source activity type. Custom Activity types beyond Nutshell's defaults must be added before Activities referencing them are imported.If skipped: Activities referencing an undefined Activity type are rejected at import.
  • Pause Sync email under Settings until cutover completes. Sync email automatically threads incoming and outgoing mail against People and Companies. Leaving it active during import can attach mid-load Activities to half-loaded People.If skipped: Email sync firing on partially-loaded data scrambles thread-to-record associations.
  • Disable outbound integrations (Zapier, Make, calendar sync) during import. Reconnect after Phase 5 completes. Calendar sync supports Google and Microsoft 365.
  • Announce the source-system freeze date to all end users. Send the announcement at least two weeks ahead with the exact freeze timestamp and the Nutshell go-live time.
  • Schedule a Nutshell basics training session for each end-user role. Cover Lead navigation, Pipeline progression, Activity logging, and Sync email setup. Run the session in the week before cutover, not after.
  • Designate first-responders for the first 48 hours after cutover. Name two admins and one Nutshell-fluent power user who will triage user issues immediately. Publish their Slack handles or extensions.
  • Document the rollback decision criteria and owner. Decide who has authority to call a rollback, what data-loss threshold triggers it, and what 'rolled back' means operationally (delete imported records, restore source writes).If skipped: Without a documented rollback owner, indecision drags out a botched cutover instead of triggering a clean restart.
2. Source Export15 tasks
  • Export source contacts/persons to CSV with all standard and custom fields. Include source record ID, full name, email, phone, company link, owner email, created date, and every custom field. Encode as UTF-8.If skipped: Non-UTF-8 encoding causes Nutshell's CSV import wizard to reject the file with an immediate upload error.
  • Export source companies/accounts to CSV with all fields and the parent-company link if used. Capture the parent-company relationship so multi-level company hierarchies can be rebuilt.
  • Export source leads/opportunities to CSV with pipeline, stage, value, confidence, close date, owner, and linked person and company IDs. Capture both source record ID (for traceability) and linked person/company source IDs so relationships can be rebuilt in Nutshell.If skipped: Without source IDs, you cannot reconnect Leads to their People and Companies after the lookup IDs change in Nutshell.
  • Export source activities (calls, meetings, emails) to CSV with type, subject, due date, due time, duration, owner, and linked record IDs. Map source activity types to the Nutshell Activity types defined in Phase 1b.
  • Export source notes with body, created date, author, and linked record IDs. Notes feed Nutshell's timeline and the Power AI timeline summarisation feature, so chronological order matters.
  • Export source tasks with subject, due date, owner, and linked record IDs. Nutshell distinguishes Tasks (action items with due dates) from Activities (logged events). Keep them in separate export files.
  • Export source products/catalog items with code, name, unit price, and currency. These feed the Product Importer in Nutshell and the Product custom-field type on Leads.
  • Export the user list with full name, email, role, and reporting hierarchy. Used to provision Nutshellers in Phase 1b and to map source owner_id to destination owner email.
  • Export source pipeline definitions: pipeline name, stages, stage order, confidence percentages. These power the pipeline-rebuild task in Phase 3d.
  • Export source Sources, Markets, and Industries reference values. These are reference lists in Nutshell at the company level; capture the distinct values referenced by Leads and Companies.
  • Export source competitor records if a Competitors object exists in the source. Nutshell has a Competitors object. Map only if the source carries equivalent data.
  • Export source email-sequence definitions as documentation, not data. Nutshell's Email sequences and Templates do not import as data; capture trigger conditions, templates, and step delays for manual rebuild.
  • Export every source attachment along with its parent record ID and original filename. Capture both the binary file and the metadata mapping it to its parent record.If skipped: Without the mapping file, attachments arrive in Nutshell unlinked and require manual re-attachment.
  • Export reports, Activity Reports, and Forecast configurations as documentation only. Reports must be rebuilt manually after cutover in Nutshell's Activity Reports and Forecast views.
  • Stamp every export file with its exact UTC export timestamp. The timestamp defines the delta that the cutover final-pull (Phase 5) must capture.If skipped: Without an export timestamp you cannot tell what activity occurred between Phase 2 and cutover.
3. Transform & Map27 tasks
  • Build a master mapping spreadsheet covering every source field for every object. Columns: source object, source field, source type, destination object, destination field, destination type, transformation rule, nullability, mandatory-at-import flag.If skipped: Without a single source-of-truth mapping document, field decisions get made twice and the second decision overwrites the first silently.
  • Mark Nutshell mandatory fields per object: Person name; Company name; Lead title. Confirm every source row will satisfy these. Build a pre-import validator if you have more than 10,000 rows.If skipped: Mandatory-field violations are the most common cause of error rows during Nutshell CSV imports.
  • Resolve every reference-list value mismatch between source and destination. Source 'Won-Closed' must become destination 'Won' on the Stage list; source 'WEB' must become destination 'Website' on the Source list. Build the mapping table inline in the master spreadsheet so transforms reference one location.
  • Designate the upsert key per object: email for People, domain for Companies, source record ID held in a custom field for Leads. Nutshell's duplicate matcher checks exact name first, then email — for re-runs to be idempotent the upsert process must mirror that or stamp a known external ID into a Text custom field.If skipped: Re-running an import without a stable upsert key duplicates every record instead of updating it.
  • Decide handling for source fields with no Nutshell equivalent. Options per field: drop, concatenate into Notes, or create a Nutshell custom field. Document the choice for every orphan field.
  • Decide handling for source records whose owner email does not exist as a Nutsheller. Either provision the missing Nutsheller before import, reassign to a 'Migration' Nutsheller, or drop the record. Document the rule.
  • Convert all date and datetime values to ISO-8601 with explicit timezone. Format YYYY-MM-DD for Date fields and YYYY-MM-DDTHH:MM:SSZ for datetime fields. The CSV import wizard parses ISO-8601 unambiguously.If skipped: Ambiguous DD/MM vs MM/DD strings get parsed by the importer's locale and silently shift dates by months.
  • Normalize currency values: strip thousand separators and force a decimal point. Currency custom fields and Lead value fields expect numeric input; symbols like $ or € get rejected.
  • Truncate Text custom-field values to 225 characters. Nutshell Text custom fields cap at 225 characters. Use Long Text for anything longer.If skipped: Text values over 225 characters are silently truncated, losing the tail with no error message.
  • Re-encode every text field as UTF-8. Nutshell's import requires UTF-8; non-UTF-8 files produce an error page immediately after upload.If skipped: Non-UTF-8 encoding rejects the entire file, not single rows.
  • Escape commas, quotes, and newlines inside CSV cells per RFC 4180. Wrap any cell containing a comma, quote, or newline in double quotes and double-up internal quotes.If skipped: Unescaped commas split rows into wrong column counts and the import wizard rejects the row.
  • Map Decision custom-field values to the destination's option labels exactly. Case and whitespace must match the destination Decision option exactly. A trailing space rejects the field-level write.If skipped: A trailing space or wrong capitalization on a Decision option label drops the value silently.
  • One column per field: separate first name from last name, city from country. Nutshell's CSV best practices require each piece of information in its own column for the mapping wizard to resolve cleanly.
  • Ensure each CSV row carries exactly one record's data. Multi-row records (e.g. a Person with several emails on adjacent rows) confuse the import wizard. Concatenate or split before upload.
  • Decide strategy for preserving the original record creation timestamp. Nutshell stamps the created-at field with the import moment. To preserve the source created date, store it in a custom Date field named 'Source Created Date'.If skipped: Reporting that filters on created-at will treat every migrated record as created at cutover, distorting historical trend analysis.
  • Decide strategy for record ownership: best-match by source owner email, or assign all to a single 'Data Migration' Nutsheller. If using best-match, ensure every source owner email exists as a Nutsheller before import (see Phase 1b).
  • Decide strategy for file attachments: re-upload binaries or preserve as external storage links. Re-upload preserves in-app access but consumes upload time. External links keep files outside Nutshell and make them dependent on the source storage layer.
  • Pre-sort the load order: Nutshellers, Products, Sources/Markets/Industries, Companies, People, Leads, Activities, Notes, Tasks, Files. Children cannot reference parents that do not exist yet; this order respects every Nutshell dependency.If skipped: Loading Leads before Companies strands Leads without their Company link and forces a re-link pass after.
  • Map source contact, account, and opportunity objects to Nutshell People, Companies, and Leads. Nutshell's object model is People (individuals), Companies (organizations), Leads (sales opportunities), and Accounts (existing customer relationships if used). Map every source object explicitly.If skipped: Conflating Leads with Accounts puts active sales opportunities and closed-customer records in the wrong list views.
  • Rebuild every Pipeline and Stage in Nutshell with confidence percentages before importing Leads. Nutshell supports multiple Pipelines per sales process. Each Stage carries a confidence percentage (0–100) that drives Forecast math; the destination percentages must match source intent.If skipped: Importing Leads into a Pipeline with mis-set confidence percentages distorts every forecast report from day one.
  • Map source Decision-equivalent fields (Yes/No, multi-choice) to Nutshell's Decision custom-field type. Define the destination Decision options ahead of the import. Values that do not match the destination option list silently fail.
  • Populate Sources, Markets, and Industries reference lists from the source distinct-value snapshot. Nutshell uses Sources for attribution, Markets for segmentation, and Industries for vertical classification. Every value an imported Lead or Company references must already exist on the destination list.If skipped: Missing reference values are silently dropped from the imported record with no field-level error surfacing.
  • Plan the rebuild of every Email sequence and template manually in Nutshell. Source sequences and templates do not migrate. Capture trigger conditions, step delays, and template content during Phase 2 and rebuild in Nutshell. Leave sequences paused until validation completes.If skipped: Activating sequences before validation triggers email blasts to customers on incorrect data.
  • Plan Goals migration manually based on the Phase 0 success criteria. Nutshell Goals are configured per Nutsheller and per team. Source quotas do not auto-translate; document the new Goals before opening Nutshell to end users.
  • Plan Sync email setup as a per-Nutsheller post-cutover task. Sync email is configured per user under Settings. Pre-configure the global blocklist (HR, payroll, investor, legal domains) before users connect their inboxes.
  • Map source contact-merge logic to Nutshell's exact-name-then-email matcher. Nutshell merges on exact name first, then falls back to email. If source data has people with the same name but different emails, the matcher merges them into one record.If skipped: Two distinct John Smiths in the source land as one merged Person in Nutshell unless the import deliberately bypasses the matcher.
  • Rebuild Activity Reports and Forecast configurations from the Phase 2 documentation. Reports do not migrate. Build the destination versions against the new field names and verify totals against the Phase 6 validation report.
4. Sandbox Test Migration13 tasks
  • Load a 1–5% representative sample of each object into the sandbox or trial tenant. Use Settings > Data > Import for the CSV import wizard for People, Companies, Leads, Activities, Notes, and Tasks.If skipped: Skipping a sample run means production becomes the first place errors surface.
  • Trigger every Decision option value at least once in the sample. If a Decision field has 20 options, the sample should exercise all 20 so option-mapping errors surface here, not in production.
  • Verify 5–10 random sandbox records field-by-field against the source. Walk every custom field, every Decision value, and every linked record. Document and triage every mismatch.
  • Test edge cases: 225-character text, multi-line notes, emoji, RTL languages, leading/trailing whitespace, NULL values. Each of these has historically broken at least one CRM importer; verify Nutshell's behavior on yours.
  • Test Currency custom-field import with at least one non-default currency value. Confirms the field accepts the numeric values your transform produces.
  • Test parent-child relationships: Company with People, Person with linked Company, Lead with linked Person and Company. Open the imported Lead in Nutshell and confirm Person and Company are populated correctly.If skipped: Broken links are invisible from the Lead list view but show as empty Person/Company columns in reports.
  • Test Activity-to-Lead and Activity-to-Person linkage on the sample. Activities without correct lead_id or person_id render orphan on the timeline.
  • Test the Stage assignment for at least one Lead per Pipeline. Confirms Stage names mapped correctly and confidence percentages render as expected.
  • Test file attachment upload for representative file sizes. Confirm both small files (under 1 MB) and large files (over 10 MB) attach and render correctly.
  • Time the sample run end-to-end and extrapolate to full volume. Capture seconds per record per object, including retries. The 100-record reference sample size used by some import utilities is a useful baseline for extrapolation.If skipped: Extrapolation from a 50-row sample without considering throughput ceilings produces a cutover estimate off by an order of magnitude.
  • Confirm the past-imports list in Settings > Data > Import shows the sandbox run. Verifies that Nutshell records the sandbox import as a discrete event you can reference for rollback diagnosis.
  • Have a sales-ops or RevOps power user spot-check 20 sandbox records. They will catch business-logic issues (wrong Stage, wrong owner, missing Source) that field-level checks miss.
  • Get written sandbox sign-off before proceeding to Phase 5. Sign-off names the test artifacts (record counts, sampled records, edge-case results) and is the gate to production.If skipped: Skipping sign-off lets unresolved sandbox issues carry into production where the cost of fixing them rises.
5. Production Cutover16 tasks
  • Confirm the source-system freeze is in effect; verify no writes in the last hour. Audit the source change log if available, or sample 10 recent records and confirm modified_at timestamps are all before freeze.If skipped: Late writes after the freeze produce records that exist in source but not in destination, requiring a manual delta pass.
  • Take a final full export to capture the delta since the Phase 2 baseline. Diff the new export against the Phase 2 export and load only changed/new rows to minimize load time.
  • Confirm Sync email is paused, Email sequences are inactive, and outbound integrations are disconnected. Re-verify Phase 1b: Sync email, Email sequences, Zapier/Make connections, and calendar sync are all off.If skipped: A single live sequence can send hundreds of customer emails during the load.
  • Load Sources, Markets, and Industries reference values via Settings. These must exist before any Lead or Company referencing them is loaded.
  • Load Products through the Product Importer, capturing returned IDs into a lookup file. Leads will reference these Products through the Product custom-field type.
  • Load Companies via the CSV import wizard, capturing returned IDs. Build company_source_id -> company_nutshell_id lookup file for downstream loads.
  • Load People with company_id populated from the lookup. Use the CSV import wizard with the Company column referencing the destination Company name or ID.
  • Load Leads with person_id, company_id, pipeline_id, stage_id, value, confidence, owner, and close-date set. Use stage_id from the pipeline rebuild lookup, not stage_name.If skipped: Posting stage_name instead of stage_id silently puts the Lead in the default Stage.
  • Load Activities with lead_id, person_id, company_id, type, due_date, and completed flag. Completed Activities should carry the source completion timestamp where the importer supports overriding it.
  • Load Notes with lead_id, person_id, or company_id and created-at set to the source created timestamp where supported. Notes feed the timeline view and Power AI summarisation; chronological order matters.
  • Load Tasks with assigned Nutsheller, due date, and parent record ID. Tasks are distinct from Activities in Nutshell; load them as a separate pass.
  • Upload File attachments last with the parent record ID required on each upload. Files arrive last because their parent records must exist first.
  • Capture every import job's row count, success count, error count, and error log. Build a job-status file the Phase 6 reconciliation reads from. Cross-reference against Settings > Data > Import history.If skipped: Without per-job error logs you cannot tell which records failed and need a re-run.
  • Cross-check destination counts against source counts after each object-type load completes. If the delta exceeds your tolerance (often 0.1%), stop and diagnose before loading the next type.If skipped: Pushing through with a known delta means later types reference records that should not exist.
  • If any load step fails partway, stop, diagnose, fix the transform, and re-run idempotently against the upsert key. Idempotent re-runs depend on the upsert key (email, domain, or external-ID custom field) being captured from the partial success.
  • Re-enable Sync email, Email sequences, and outbound integrations only after Phase 6 sign-off. Reactivation order: integrations first (so they fire on subsequent changes), then Sync email per user, then Email sequences.
6. Validate20 tasks
  • Compare total record count per object: source vs Nutshell. Pull counts from Nutshell list views for People, Companies, Leads, Activities, Notes, Tasks, and Products. Compare to the Phase 1 baseline.If skipped: An unexplained delta indicates either error rows you missed or a parent-link failure that orphaned children.
  • Compare aggregate open Lead value: source vs Nutshell. Group Leads by status=open and pipeline_id, sum value. Investigate any delta over 0.5%.
  • Compare won-Lead count and aggregate value for the last 12 months. Won-Lead counts power most sales reporting; a delta here surfaces Stage-mapping errors.
  • Spot-check 25–50 randomly selected Leads field-by-field against source. Walk every standard field and every custom field on each sampled Lead.
  • Spot-check 25 randomly selected People including all custom fields. Validates the Person schema separately from the Lead schema.
  • Compare Lead counts per pipeline-stage between source and Nutshell. A stage-by-stage diff surfaces Stage-mapping errors that aggregate totals hide.If skipped: Two stages that net to the same total but moved Leads to the wrong bucket distort forecasts.
  • Verify confidence percentages on every Stage match the source intent. Confidence drives Forecast math; a 10-point mistake on one Stage propagates to every Forecast view.
  • Verify a random sample of 30 person-to-company associations match source. Confirms company_id populated correctly on People rows.
  • Verify a random sample of 30 Lead-to-Person and Lead-to-Company links. Confirms person_id and company_id populated correctly on Lead rows.
  • Verify a random sample of 30 Activity-to-Lead links. Confirms lead_id populated correctly on Activity rows; orphan Activities render on the timeline but not on the Lead.
  • Verify Sources, Markets, and Industries values populated on a sample of imported Leads and Companies. Missing reference values are the single most common silent failure mode in Nutshell imports.If skipped: Missing reference values reduce Forecast and segmentation reporting accuracy without an obvious error symptom.
  • Confirm file attachments are accessible and bound to the correct record. Open 20 random attached files from inside their parent Lead/Person/Company to verify both linkage and binary integrity.If skipped: Files that uploaded successfully but linked to the wrong record are invisible without per-record inspection.
  • Verify the Source Created Date custom field is populated on every migrated record. Confirms the audit-trail strategy from Phase 3c worked end-to-end.
  • Run a GDPR access-request rehearsal on a test contact. Confirms the new tenant's data-subject-access flow works against migrated data.
  • If on Enterprise, confirm Audit Log captures the import events. The Audit Log is Enterprise-only. Verify logins, bulk edits, and exports during the cutover window are recorded.If skipped: Discovering the Audit Log is empty after go-live means there is no forensic trail of the cutover itself.
  • Confirm Nutshell's region matches the contractual residency commitment. Validates the Phase 0 residency check against the actual provisioned tenant.
  • Have 3–5 power users complete their daily workflow end-to-end in Nutshell against migrated data. Examples: log in, find a Lead, add a Note, log a call, advance Stage, send email via Sync email.
  • Document every issue raised in UAT with severity (blocker / important / cosmetic). Blockers must be resolved before Phase 7; cosmetic items go to the 30-day backlog.
  • Confirm Activity Reports and Forecast views reflect expected totals on at least three pre-agreed reports. Open pipeline by owner, Leads won this quarter, Activities completed this week.
  • Get written sign-off from the migration sponsor before opening Nutshell to end users. Sign-off references the reconciliation report, UAT log, and the compliance checks above.If skipped: Opening to users before sign-off means data errors get found by sales reps mid-call, eroding trust in the new system.
7. Post-Migration Cleanup12 tasks
  • Announce Nutshell go-live to all end users with login URL, support contact, and the source read-only date. Include a one-pager pointing to the most common 'where did this go' translations between source UI and Nutshell UI.
  • Run the planned end-user training sessions by role (sales rep, sales manager, ops). Use migrated data live in the sessions so users see their own records, not toy examples.
  • Set the source system to read-only on the announced date. Read-only mode preserves it as a reference but prevents drift between source and Nutshell.If skipped: Leaving the source writable creates two sources of truth and reps will use whichever is faster, scrambling the data again.
  • Rebuild every Activity Report, Forecast view, and saved filter in Nutshell. Reports do not migrate. Rebuild against destination field keys and confirm totals against the Phase 6 validation report.
  • Recreate every Email sequence and Template manually, then reactivate one at a time monitoring for unintended sends. Start with low-risk internal-only sequences. Watch sends for a day before activating customer-facing sequences.If skipped: Activating all sequences at once on freshly loaded data can fire bulk customer emails referencing stale context.
  • Recreate Goals per Nutsheller and per team based on the Phase 0 success criteria. Goals do not migrate; configure them in Settings before the first end-of-quarter review.
  • Have each Nutsheller connect Sync email under their account settings. Nutshell does not bulk-enable Sync email; each user connects Gmail, Microsoft 365, or Exchange individually. Verify the global blocklist applied in Phase 1b is enforced.
  • Reconnect outbound integrations: Zapier, Make, BI tools, calendar sync. Restore in the order they were paused; verify each integration sees migrated records correctly.
  • Archive Phase 2 source-system exports to long-term cold storage with documented retention. Retain for the duration of your compliance window in case forensic comparison is needed.
  • Schedule a 30-day post-migration retrospective. Invite the DRI, sponsors, first-responders, and 2–3 end users. Capture what worked, what hurt, and what to do differently next time.
  • Decide and document the source-system decommission date. Typically 90 days after cutover, after the final compliance retention window. Confirm contract terms before fully shutting it down.
  • Close the migration project formally. Final status report, lessons-learned doc, and project closure ticket. The migration is not done until this exists.

Questions, answered

Migrating to Nutshell: questions

How long does migration to Nutshell take?

A small-business migration with under 5,000 People and standard fields runs one to two business days end-to-end. A mid-market project with multiple pipelines, custom Decision fields and historical activities runs two to four weeks of elapsed time, including preparation, dry runs in a trial workspace, validation, training and a 48-hour hyper-care window.

Can I migrate from Salesforce to Nutshell?

Yes — Nutshell ingests Salesforce's Setup → Data Export .zip file directly through the Import2-powered Another CRM path. Standard objects map cleanly, but Apex code, Flows, Process Builder and Reports do not transfer and need to be rebuilt natively. Watch for Salesforce's once-monthly export cap on lower editions.

Can I migrate from HubSpot to Nutshell?

Yes. The Import2-powered Another CRM path inside Nutshell supports HubSpot as a source for Contacts, Companies, Deals and Activities, mapping them to Nutshell's People, Companies, Leads and Activities. Watch HubSpot picklist internal values vs display labels and rebuild HubSpot workflows as Nutshell email sequences and saved automations.

Can I migrate from Pipedrive to Nutshell?

Yes, and Pipedrive-to-Nutshell is usually one of the cleanest migration shapes because the object models align — People, Organisations, Deals and Activities correspond to Nutshell's People, Companies, Leads and Activities. Recreate each Pipedrive pipeline as a Nutshell pipeline before importing, and watch Decision-field value casing during transform.

Does Nutshell preserve original timestamps on import?

Partially. Activity dates on Calls, Meetings, Logged Emails, Notes and Tasks can be backdated and show up correctly on the People, Companies and Leads timeline. But Nutshell-managed system fields like record created date and modified date cannot be overridden — use custom Legacy Created Date fields to preserve the original audit trail.

What's the difference between using the CSV wizard and the Import2 path for Nutshell?

The CSV wizard handles People, Companies and Leads with a visual mapping step and is best for one-shot loads under tens of thousands of records. The Import2-powered Another CRM path supports common SaaS sources end-to-end with relational context, free 100-record sample runs, and Salesforce .zip ingestion.

Can I migrate Custom Fields to Nutshell?

Yes, but you must pre-create every custom field with the right type — Text, Long Text, Currency, Date, Email, Decision, Address, Phone, URL, or Product — on the right object before importing. Decision-field option values must also be pre-loaded. Custom-field counts are plan-tier gated, so verify your cap first.

What happens to lead history and pipeline stages during migration?

Recreate every pipeline and every stage name in Nutshell before importing Leads — rows targeting non-existent stages land in the pipeline's default stage with no warning. Stage transition history is not auto-preserved; if you need it for reporting, export stage-entered timestamps from the source and store them in custom Date fields.

Get a quote

Moving to Nutshell?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Nutshell setup with you, then send a quote.

Get a quote