Migrate from Nurture to Nutshell

Discovery and Nurture audit

We audit the source Nurture portal for all standard objects (Contacts, Companies, Deals, Activities, Tasks), custom field definitions, active user count, owner assignments, and any active workflow configurations. We capture the current usage-based service billing summary (average call minutes, SMS count, email volume over the past three months) so the customer has a reference point for Nurture account cancellation. The discovery output is a written scope confirming record counts, custom field inventory, and any workflow or automation features that require separate rebuild documentation.

Nutshell workspace preparation

We set up the destination Nutshell workspace. This includes provisioning custom fields on Person, Company, Lead, and Deal objects to receive any mapped custom values from Nurture, configuring the Deal pipeline and stage names to match the Nurture setup as closely as possible, and creating a Nutshell User record for each Nurture Owner by email. We validate that all required Nutshell custom fields exist with the correct data types before any data import begins.

Sandbox migration and reconciliation

We run a test migration into a Nutshell staging environment using a representative sample of production data (typically 10-15% of total records). The customer reviews 25-50 spot-checked records against the Nurture source and validates that Person records are correctly linked to Company, Deal records are linked to the correct Person, and activity timestamps are preserved. Any mapping corrections happen in this phase. We do not proceed to production until the customer signs off on the sandbox results.

Owner reconciliation and User provisioning

We extract every distinct Nurture Owner email from Contacts, Companies, and Deals and match against Nutshell User records by email. Any owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision. OwnerId references must be resolvable before record import because Nutshell requires a valid owner on Deal and Person records.

Production migration in dependency order

We run production migration in record-dependency order: Nutshell Users (manual, validated), Companies (from Nurture Companies), Persons (with CompanyId resolved), Deals (with PersonId and OwnerId resolved), and Activities/Tasks (consolidated into Nutshell Task via Bulk API with TaskSubtype set per activity type). Each phase emits a row-count reconciliation report before the next phase begins. Custom field values insert in the same pass as their parent object.

Cutover, validation, and workflow handoff

We freeze Nurture writes during cutover and run a final delta migration for any records modified during the migration window. We enable Nutshell as the system of record once delta validation confirms zero new records pending. We deliver the Nurture workflow inventory document to the customer's admin with recommended Nutshell equivalents. We offer a one-week hypercare window to resolve any reconciliation issues raised by the team. We do not rebuild Nurture workflows as Nutshell automations inside the migration scope; that is a separate engagement.