Migrate from Vaulta to Nutshell

Vaulta lifecycle stages have no native Nutshell equivalent and require a custom field

Vaulta's configurable lifecycle stages (e.g., Prospect, Qualified, Customer, Evangelist) are defined per object type and can be set to any pick-list value your team has configured. Nutshell does not have a native equivalent field on Person or Lead records. We migrate the lifecycle value as a custom pick-list field on the relevant Nutshell object, preserving the exact Vaulta label. If your Vaulta setup uses different lifecycle fields on different objects (e.g., one lifecycle for people, another for companies), each requires a separate Nutshell custom field. The stage-transition history is preserved as an audit note field in Nutshell so your team can see the last Vaulta lifecycle value even after records are updated.

Vaulta N:N person-to-company associations collapse to a single primary company in Nutshell

Vaulta supports many-to-many person-to-company relationships natively — a single person record can be associated with multiple Vaulta companies simultaneously. Nutshell models each Person with exactly one primary Company. We assign the most-recently-modified Vaulta company association as the Nutshell primary and surface all other associated Vaulta company IDs in a custom reference field. Your Nutshell admin reviews this after migration and decides whether to rebuild secondary company links manually using Nutshell's Company relationship feature. Any Vaulta company-person link that represents a different business role (e.g., a board member at one company and an advisor at another) requires manual reconstruction in Nutshell's CRM.

Vaulta file attachments and documents are re-uploaded to Nutshell Files — original URLs cannot be preserved

Vaulta's document layer lets users attach files directly to Vaulta records. When migrating to Nutshell, files are downloaded from Vaulta storage and re-uploaded via the Nutshell Files API. The original file name, file size, and Vaulta upload timestamp are preserved as Nutshell File metadata. However, the original Vaulta file URL cannot be preserved — any links pointing to Vaulta-hosted files break after migration. We recommend reviewing all Vaulta file links in your CRM records before the cutover and updating any hyperlinks or documents that reference external Vaulta URLs to point to the new Nutshell File locations.

Vaulta deal stage values may not map 1:1 to Nutshell deal stages

Vaulta allows your team to define custom deal stages with arbitrary names and probabilities. Nutshell Deal Stages are configured per pipeline and use a fixed pick-list model. We map each Vaulta deal stage to the closest Nutshell stage name — if no close match exists, we flag the Vaulta stage for manual mapping before the full migration runs. Stage probability from Vaulta is not automatically applied to the Nutshell stage probability because Nutshell computes probability at the stage level, not the record level. We include a stage-mapping table in the migration plan that your Nutshell admin reviews and approves before data lands.

Vaulta lead status values may require value-by-value mapping to Nutshell Lead Status

Vaulta lets administrators configure custom lead status pick-list values beyond Nutshell's standard set (New, Contacted, Qualified, Lost). We map Vaulta custom lead status values to the closest Nutshell standard status. Any Vaulta lead status that has no clear Nutshell equivalent is flagged in the migration plan — your team decides whether to use the closest standard status, create a custom lead status in Nutshell (which is supported on Pro and Business plans), or accept the nearest match. We also preserve the original Vaulta lead status label as a custom reference field on the Lead record for audit purposes.