Migrate from Wyvern Magic to Nutshell

Discovery and scope definition

We audit the Wyvern Magic tenant across record types (Contacts, Leads, Companies, Deals), custom properties, pipeline definitions, engagement volume, and active segmentation rules. We pair this with a Nutshell edition review: Pro ($42/user) covers single-pipeline migrations; Enterprise ($79/user) is required if Wyvern Magic uses multiple pipelines or the customer needs API access for third-party integrations. The discovery output is a written migration scope, a Nutshell edition recommendation, and a custom object redistribution plan.

Custom field map and type inference

We inspect Wyvern Magic's custom properties on each standard object and generate a type-mapped field map for Nutshell. Text properties map to Nutshell text fields, numbers to number fields, dates to date fields, and picklists to Nutshell picklist fields. Custom object fields distribute to Person, Company, or Deal based on their logical owner. The customer reviews and approves the field map before any schema changes are made in Nutshell.

Pipeline and stage configuration in Nutshell

We configure the Nutshell pipeline and stages before record migration. Stage names, probabilities, and order match the Wyvern Magic source. If multiple pipelines exist and Enterprise is selected, we configure all pipelines. If Pro is selected and multiple pipelines must consolidate, we document the consolidation mapping and get sign-off. We test that deals can move through the pipeline stages correctly before migrating any record data.

Owner reconciliation and user provisioning

We extract every distinct Wyvern Magic owner referenced on Contacts, Companies, and Deals and match by email address against the Nutshell destination's user list. Owners without a matching Nutshell user go to a reconciliation queue. The customer's admin provisions any missing users in Nutshell before record import. Migration cannot proceed past this step because owner assignments are required on most record types.

Production migration in dependency order

We run production migration in record-dependency order: Companies first (no dependencies), then Persons (from Wyvern Magic Contacts and Leads with the Lead flag configured), then Deals (with owner and Company lookups resolved), then Activity history (linked to the correct Person, Company, or Deal). Custom object data loads as custom fields on the relevant standard object during each phase. Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, validation, and automation handoff

We freeze Wyvern Magic writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the segmentation rule and workflow inventory document to the customer's admin team with a rebuild guide for Nutshell's automation rules. We support a brief hypercare window where we resolve any reconciliation issues. We do not rebuild Wyvern Magic automations in Nutshell as part of the migration scope.