Migrate from Advantage HITS to Nutshell

Discovery and scoping

We audit the Advantage HITS account via authenticated session access, enumerating all Contact, Company, Deal, Pipeline, Activity, Attachment, Tag, and User records. We document custom field names, types, and visibility settings; capture the full pipeline definition including stage names, ordering, and win/loss flags; and generate a record count report. We also confirm the Nutshell account tier (Starter, Growth, or Enterprise) and identify any limitations that affect the import scope, such as the absence of API access on Starter or Growth tiers or the 10 MB attachment limit. The discovery output is a written migration scope document covering record counts, custom field inventory, and a preliminary stage mapping matrix.

Schema preparation in Nutshell

We create all custom fields in Nutshell (available on Growth and Enterprise tiers) using the names and types identified during discovery. We configure the Nutshell pipeline stages to match the Advantage HITS stage names and ordering, obtaining customer sign-off on the final stage mapping matrix before proceeding. Any Advantage HITS stage names without a direct Nutshell equivalent are resolved with the customer, and the agreed mapping is documented. Nutshell's default pipeline is used for Starter and Growth accounts; Enterprise accounts use the single default pipeline unless multiple pipelines are explicitly required.

Data extraction from Advantage HITS

We extract records from Advantage HITS via authenticated session access using the credentials provided by the customer. Data is extracted in dependency order: Users first (for owner remapping), then Accounts (from Companies), then Contacts (with AccountId resolved), then Deals (with stage name mapped), then Activities, then attachments. Large record sets are chunked to avoid session timeout. We generate a data quality report identifying missing required fields, empty values, and stage names not present in the pipeline definition. Corrections are resolved with the customer before the import phase begins.

Batch import into Nutshell

We import records into Nutshell using the spreadsheet import in batches of up to 500 rows per file. Each batch is validated against Nutshell's field requirements and picklist constraints before submission. Import proceeds in record dependency order: Accounts first (as the parent of Contacts), then Contacts (with AccountId resolved to the imported Account), then Deals (with stage name matched to the Nutshell stage value), then Activities, then tags. Owner assignments resolve via email match to the Nutshell User table; unresolved owners are queued for admin reconciliation. Each import batch produces a row-count reconciliation report comparing imported rows to exported rows.

Attachment migration and post-import validation

We download file attachments from Advantage HITS using the authenticated session, preserving original filenames and file metadata. Files under 10 MB are uploaded to the destination Nutshell record via the Nutshell UI or API (Enterprise only). Files exceeding 10 MB are listed in the reconciliation report with source record reference for manual re-upload. We run a post-import validation comparing record counts between the exported and imported datasets, spot-checking 25-50 records against the source for field-level accuracy. Any discrepancies are corrected before the final cutover.

Cutover and handoff

We freeze write access to Advantage HITS during the cutover window and run a final delta extraction for any records modified during the migration. Nutshell becomes the system of record once the final delta import completes and the customer confirms data accuracy. We deliver the complete Workflow and Automation inventory (documented from the Advantage HITS UI during discovery) to the customer's admin team, along with a rebuild guide identifying equivalent Nutshell automation options for each documented rule. We support a one-week hypercare window for reconciliation issues raised during the first five business days of Nutshell use. Workflow rebuilds, automation configuration, and admin training are outside standard migration scope.