Migrate from Wyvern Magic to Microsoft Dynamics 365 Sales

Discovery and schema inventory

We audit the Wyvern Magic tenant across custom properties, pipeline definitions, active workflow rules, owner assignments, and record volumes per object. We pair this with a Microsoft Dynamics 365 Sales edition assessment: Sales Professional ($65/user) covers most migrations without complex custom objects; Sales Enterprise ($105/user) is required if the customer needs advanced forecasting, conversation intelligence, or multi-org Dataverse architecture. The discovery output is a written migration scope document, a field-level mapping table, and a Dynamics 365 edition recommendation.

Sandbox schema provisioning and pipeline configuration

We create the destination schema in a Dynamics 365 Sandbox (or Dev environment). This includes provisioning custom entities for Wyvern Magic custom objects, creating custom columns for custom properties, creating Sales Process stage values matching the Wyvern Magic pipeline stages, and creating Record Types on Opportunity for each Wyvern Magic pipeline. The customer validates the schema before production migration begins.

Data quality assessment and deduplication

We run a data quality assessment against the Wyvern Magic source: duplicate detection on email and domain fields, required-field completeness scoring, and stale-record flagging. We deliver a remediation report and recommend a deduplication pass (record suppression or merge) before the production migration run. Skipping this step means duplicate Accounts, incomplete Contacts, and stale Opportunities land in Dynamics 365 on day one.

Owner reconciliation and User provisioning

We extract every distinct Wyvern Magic Owner referenced on Contacts, Companies, Deals, and Leads and match by email against the Dynamics 365 destination User table. Owners without a matching User go to a reconciliation queue. The customer's admin provisions any missing Users (active for current owners, inactive for departed owners if historical attribution is required). Migration cannot proceed past the parent record phase until all OwnerId references have a valid destination User.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from Wyvern Magic Companies), Contacts (with AccountId resolved), Leads (with OwnerId resolved), Opportunities (with AccountId, ContactId, OwnerId, and RecordTypeId resolved), Activity history (Tasks, Emails, PhoneCalls, Appointments via Dataverse batch API with parent-record resolution), Custom Objects (last, after all standard parent records exist). Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, validation, and workflow rebuild handoff

We freeze Wyvern Magic writes during cutover, run a final delta migration of any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record. We deliver the Workflow and Automation inventory document to the customer's admin team for rebuild in Microsoft Dynamics 365 Sales workflows or Power Automate. We support a one-week hypercare window for reconciliation issues. We do not rebuild Wyvern Magic workflows inside the migration scope; that is a separate engagement.