Migrate from Wyvern Magic to HighLevel

Wyvern Magic Contacts map directly to GoHighLevel Contacts. Standard fields (name, email, phone, address) migrate 1:1. Custom contact properties from Wyvern Magic migrate as GoHighLevel Contact custom fields, with a type-inference step assigning the correct GoHighLevel field type (text, number, date, picklist). Lifecycle stage assignments from Wyvern Magic preserve as a custom Contact field for segmentation in GoHighLevel workflows.

Wyvern Magic Company records map to GoHighLevel Company records. The company domain becomes the Company Website field and is used as a deduplication key during import. Associations to Contacts are preserved by linking Contact records to the migrated Company via GoHighLevel's contact-company relationship after both objects are imported.

Wyvern Magic Deals map to GoHighLevel Opportunities. The deal stage property maps to the GoHighLevel Pipeline stage, and the pipeline assignment maps to a GoHighLevel Pipeline that we create before migration. Deal value, close date, owner assignment, and any associated custom fields migrate to Opportunity custom fields.

Each Wyvern Magic deal pipeline becomes a GoHighLevel Pipeline with stage entries. Stage names and probabilities migrate as GoHighLevel stage definitions. If Wyvern Magic uses custom probability values per stage, we configure those in GoHighLevel's stage probability settings.

Wyvern Magic Lead records map to GoHighLevel Contacts tagged with a 'Lead' status label. Lead source, status, and rating fields from Wyvern Magic migrate as Contact custom fields. GoHighLevel does not have a separate Lead object by default; unqualified prospects live as Contacts with status managed via tags or custom fields.

Wyvern Magic custom object schemas migrate to GoHighLevel Custom Objects with matching API names and field structures. We pre-create the destination schema including all custom fields, lookup relationships, and unique field constraints (GoHighLevel supports up to 10 unique fields per object). Custom objects with required fields must have those fields populated before migration; we flag any records with missing required fields during the scoping audit.

Custom fields on standard Wyvern Magic objects migrate as GoHighLevel custom fields on the corresponding object. We perform type inference to assign the correct GoHighLevel field type: Single Line Text, Multi Line Text, Number, Phone, Date, Picklist, or Multi-Select Picklist. Tenant-specific picklist values from Wyvern Magic map to GoHighLevel picklist options.

Wyvern Magic activity records (emails, calls, meetings, notes, tasks) attached to Contacts or Deals migrate as GoHighLevel contact activities. Each activity type maps to the appropriate GoHighLevel object: emails and notes as notes or internal comments, calls as logged calls, meetings as calendar events, tasks as tasks. Activity timestamps and owner assignments preserve by linking to the migrated Contact record.

Wyvern Magic User records and owner assignments on Contacts, Deals, and Leads map to GoHighLevel Users. We resolve owners by email match. Any Wyvern Magic Owner without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Wyvern Magic tags applied to Contacts, Deals, and Companies migrate as GoHighLevel Tags. Multi-value tag arrays flatten into individual tag associations per record. GoHighLevel Tags are used to trigger workflows and segment contacts; the customer chooses whether to preserve the Wyvern Magic tag taxonomy or consolidate during migration.