Migrate from Wyvern Magic to Salesforce Sales Cloud

Wyvern Magic Contacts with early lifecycle stages (Prospect, Lead) map to Salesforce Lead. Contacts at later stages (Qualified, Customer) map to Salesforce Contact tied to an Account. We compute the split at migration time using Wyvern Magic's lifecycle stage property, and preserve the original stage in a custom field wyvern_lifecycle_stage__c on both Lead and Contact for audit and reporting continuity.

Wyvern Magic Company records map directly to Salesforce Account. The company domain or name becomes the Account's Name and Website fields. Account is created before any Contact import so that the AccountId Lookup relationship is satisfied at the moment of Contact insert. Industry, employee count, and annual revenue custom fields map to their Salesforce equivalents.

Wyvern Magic Deals map to Salesforce Opportunity. The Wyvern Magic deal stage property maps to Salesforce StageName, and the pipeline assignment maps to a Salesforce Sales Process or Record Type that we configure before migration. Deal amount, close date, and owner assignments migrate directly with OwnerId resolved via email matching against the Salesforce User table.

Each Wyvern Magic pipeline becomes a Salesforce Record Type with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from Wyvern Magic to Salesforce StageProbability, with rounding to the nearest Salesforce-allowed integer. Stage order is preserved to maintain pipeline velocity reporting.

Wyvern Magic's deal pipelines map to Salesforce Record Types on Opportunity. Each Record Type gets its own Page Layout and Sales Process so that stage values stay scoped per line of business. We extract the active pipeline definition first, then create the target configuration before any deal records are loaded.

Wyvern Magic Lead records (if the tenant uses a separate Lead object) map directly to Salesforce Lead. Lead source, status, and rating migrate directly. Any custom lead scoring fields become Salesforce custom fields. We preserve the original lead creation date and last modified date for audit continuity.

Wyvern Magic Owners map to Salesforce User records. We resolve owners by email match against the destination org's User table. Any Wyvern Magic Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive owners are migrated as inactive Users to preserve historical assignment.

Wyvern Magic email engagements migrate to Salesforce EmailMessage records (the email content) linked to an Activity Task record (the activity timeline entry). The WhoId on Task points to the converted Lead or Contact; WhatId points to the related Opportunity or Account. Email body and timestamp preserve through the Bulk API 2.0 migration pass.

Wyvern Magic call engagements map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and any recording URL transfer to custom Task fields. Activity timeline ordering is preserved by setting ActivityDate to the original Wyvern Magic timestamp. Owner assignments resolve via email-to-User matching.

Wyvern Magic meeting engagements map to Salesforce Event. StartDateTime, EndDateTime, and Location preserve. Attendee mapping links to EventRelation records pointing at the converted Leads, Contacts, and Users. Calendar-based meeting records from Wyvern Magic's calendar sync preserve as Event records with the original duration and attendee list.

Wyvern Magic Notes attached to Contacts, Deals, or Companies migrate to Salesforce Note records linked via ContentDocumentLink to the parent record. Note body migrates as plain text with image attachments preserved as separate ContentDocument records. Rich text formatting is preserved where Wyvern Magic's export format supports it.

Wyvern Magic Task engagements (reminders, to-dos, follow-ups) map to Salesforce Task with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving Wyvern Magic owner_id to Salesforce OwnerId via the User mapping. Completed status and completion dates transfer to the Salesforce Task record.

Wyvern Magic custom object schemas are tenant-specific. We inspect the schema at migration scoping, pre-create the destination Salesforce custom object (with __c API name suffix), all custom fields, lookup relationships, and validation rules, before any data import. Custom objects with required fields must have those fields populated before insert; we flag any records missing required values in the pre-migration data audit.

Custom fields on Wyvern Magic Contacts, Companies, Deals, and Leads migrate as Salesforce custom fields on the corresponding standard object. We use a type-inference step to assign the correct Salesforce data type (Text, Number, Date, Picklist, Checkbox, etc.) based on the source field's data. Multi-select picklists in Wyvern Magic map to Salesforce multi-select picklist fields.

Wyvern Magic tags applied to Contacts, Deals, and Companies migrate to Salesforce multi-select picklist fields on the corresponding object. We flatten multi-value tag arrays into the destination's picklist format. The customer chooses during scoping whether tags become multi-select picklists or Salesforce Topics with TopicAssignment records.

Wyvern Magic file attachments migrate as Salesforce ContentDocument records linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or custom object. We extract attachments from Wyvern Magic's storage, upload to Salesforce Files, and relink to the correct parent record by record ID resolution. Large file attachments may require a separate file-migration pass after the record migration completes.