Migrate from Wyvern Magic to Zoho CRM

Wyvern Magic Contacts migrate 1:1 to Zoho CRM Contacts. Standard fields (Full Name, Email, Phone, Address) map directly. Custom contact properties are migrated as Zoho CRM custom fields, with a type-inference step applied during scoping to assign the correct Zoho field type (text, number, date, picklist, multiselect). Multi-value arrays on Wyvern Magic contacts migrate as multiselect picklists in Zoho CRM.

Wyvern Magic Company records map directly to Zoho CRM Accounts. The Company domain, industry, employee count, and custom fields migrate as Account fields and custom fields respectively. Associations between Wyvern Magic Companies and Contacts are preserved via the Account-Contact link migration: Accounts are created first, then Contacts are linked during insert by matching the Company name or domain on each Contact record.

Wyvern Magic Deals map 1:1 to Zoho CRM Deals. The Wyvern Magic dealstage property maps to the Zoho CRM Deal Stage, which we provision to match the Wyvern Magic pipeline stages before migration begins. Closed-Lost reason and Closed-Won reason from Wyvern Magic custom fields become Zoho custom fields for deal loss and win reasons. The deal amount, expected close date, and owner assignment migrate as standard Deal fields.

Wyvern Magic pipeline definitions (stages, probabilities, stage order) are extracted via API before any deal record is migrated. Each Wyvern Magic pipeline becomes a Zoho CRM Pipeline with matching stage names and probability percentages. Zoho CRM's Pipeline and Stage model requires provisioning before deal insert; we complete this step during the schema design phase and validate stage coverage against the live Wyvern Magic deal data during scoping.

Wyvern Magic Lead records map directly to Zoho CRM Leads. Lead source, status, rating, and any custom lead scoring fields migrate as standard and custom Lead fields respectively. Lead scoring fields (numeric or tier-based) are mapped to Zoho CRM custom fields because Zoho's native lead scoring (Zia) is an add-on available from the Professional tier upward. Tenant-configurable lead fields are handled via the custom field mapping step.

Wyvern Magic email engagements attached to Contacts or Deals migrate as Zoho CRM Tasks with the Activity Type set to Email. Email subject, body (plain text), timestamp, and owner assignment transfer to the Task record. Emails are linked to the parent Contact or Deal via the Related To (What_Id) field. Email threading metadata migrates as custom fields if the customer requires thread reconstruction in Zoho CRM.

Wyvern Magic call engagements migrate as Zoho CRM Tasks with Activity Type set to Call. Call disposition, duration, and any recording URL stored in Wyvern Magic migrate as custom fields on the Task. Activity timestamps and owner assignments are preserved. Call tasks are linked to the parent Contact or Deal via the Related To field.

Wyvern Magic meeting engagements migrate as Zoho CRM Events. Start Date and Time, End Date and Time, and Location migrate as Event fields. Attendee mapping links to EventRelation records pointing at the associated Contacts and Users. The meeting title and any notes migrate as Event subject and description respectively.

Wyvern Magic Notes attached to Contacts, Companies, or Deals migrate as Zoho CRM Notes. Note body migrates as the Note content field. Notes are linked to the parent record via the Zoho CRM Note module's association to Contacts, Accounts, and Deals. Rich text formatting is preserved where the export format supports it.

Wyvern Magic Task engagements map directly to Zoho CRM Tasks. Task status, priority, due date, and owner assignment migrate as standard Task fields. Task subject migrates as the Task Subject field. If Wyvern Magic tasks have sub-tasks, the sub-task structure is flattened into a flat task list in Zoho CRM because Zoho's standard task model does not support hierarchical sub-tasks natively.

Wyvern Magic custom object schemas are tenant-specific and migrate to Zoho CRM custom modules. We inspect the Wyvern Magic schema at migration scoping, generate a custom field map, and provision matching custom modules in Zoho CRM before any data import. Custom modules with required fields must have those fields populated before insert; any records failing this constraint go to a separate reconciliation queue. Custom module naming follows the Zoho convention: the original Wyvern Magic custom object name becomes the Zoho module name with an underscore-C suffix if using the CSV import naming convention.

Wyvern Magic tags applied to Contacts, Deals, and Companies are migrated as Zoho CRM tag associations. Multi-value tag arrays are flattened into Zoho's tag model during import. If Wyvern Magic tags represent complex audience segmentation rules (e.g., behavioral triggers), we document them in the migration handoff notes and recommend Zoho CRM Workflow Rules or Zoho Flow equivalents for the customer's admin to implement post-migration.