Migrate from Wyvern Magic to Twenty CRM

Wyvern Magic Contacts migrate to Twenty Person records. Standard fields (name, email, phone, address) map directly. Custom contact properties are inspected during scoping, typed (text, number, date, picklist), and created in Twenty's metadata schema via the /metadata API before import. The original Wyvern Magic contact ID is preserved in a custom field for audit trail. Owner assignments map from Wyvern Magic Owner email to the Twenty workspaceMember resolved during user provisioning.

Wyvern Magic Company records map to Twenty Company. Domain, industry, employee count, and any custom company fields migrate as typed extension fields. We create the Company record before importing any Person records that reference it so that the Company lookup relationship is satisfied at insert time. Address fields on Companies map to Twenty's address compound field.

Wyvern Magic Deals map to Twenty Opportunities. The pipeline and stage configuration is extracted from Wyvern Magic first (stages, probabilities, order), then replicated in Twenty's pipeline settings before Deal records are imported. Closed-won and closed-lost reasons from Wyvern Magic custom fields become Opportunity custom fields in Twenty. Deal amount and close date map to standard Opportunity fields.

Wyvern Magic pipeline definitions (stage names, probabilities, stage order) are extracted separately from Deal records. We create the target pipeline in Twenty first, then map Deal records into the correct stage order. Stage probabilities round to integers as Twenty requires. If Wyvern Magic has multiple pipelines, each becomes a separate Pipeline in Twenty.

Wyvern Magic Lead records map to Twenty Person records. Lead source, status, and rating fields migrate as custom extension fields on the Person record. Custom lead scoring fields from Wyvern Magic transfer to a custom numeric field in Twenty. The migration does not apply any qualification logic; the customer's Twenty admin reviews the imported Persons and applies Opportunity association based on their own qualification criteria.

Wyvern Magic engagement records (email, call, note, task) migrate as linked Task and Event records in Twenty's activity timeline. Each activity is associated with the parent Person or Opportunity via Twenty's custom schema. Activity timestamps are preserved as ActivityDate. Email body content migrates as Task description. Call duration and disposition migrate as custom fields on the Task record.

Wyvern Magic custom object schemas are tenant-specific and vary by configuration. We inspect the schema at scoping, generate a custom field map with type inference, and pre-create the equivalent custom object in Twenty via the /metadata API. Any custom object with required fields must have those fields populated before migration; we flag records with missing required fields for customer review before the import phase runs.

Custom fields on Contacts, Companies, Deals, and Leads in Wyvern Magic migrate as extension fields in Twenty. We use a type-inference step to assign the correct data type (text, number, date, picklist) in Twenty's metadata schema. Multi-select picklists in Wyvern Magic map to multi-select picklists in Twenty where supported, or to tag-based fields.

Wyvern Magic Owner records map to Twenty workspaceMember records. We resolve owners by email match. Active users in Wyvern Magic become active workspaceMembers in Twenty; inactive users become inactive. Any Wyvern Magic Owner without a matching email in the destination requires manual provisioning by the Twenty admin before record migration resumes.

Wyvern Magic tags applied to Contacts, Deals, and Companies migrate as tag associations in Twenty. Multi-value tag arrays are flattened and upserted as tag records, then linked to the parent Person, Company, or Opportunity via the tag association object. Tag names are preserved exactly to maintain segmentation logic.