Migrate from Wyvern Magic to HubSpot

Wyvern Magic contacts and leads map directly to HubSpot contacts. If Wyvern Magic stores leads and contacts as separate objects, they merge into a single HubSpot Contact object. The lifecycle stage property in HubSpot captures the original record type. Email match against HubSpot users resolves owner assignment.

Wyvern Magic company or account records map 1:1 to HubSpot companies. Parent-child company hierarchies in Wyvern Magic map to HubSpot's parent company association. Multi-company associations per contact are preserved as HubSpot contact-company associations. We also preserve any corporate hierarchy depth, mapping each level to the corresponding HubSpot parent‑company link, and retain all secondary company associations on the contact record for complete relationship tracking.

Wyvern Magic deals map to HubSpot deals with pipeline and stage mapping. If Wyvern Magic uses multiple deal pipelines, each maps to a separate HubSpot deal pipeline, each with its own stage values and probability weights. The deal owner resolves by email match to HubSpot users.

HubSpot requires explicit pipeline and stage configuration. We create the pipelines in HubSpot before data lands, mapping Wyvern Magic's pipeline names to HubSpot pipeline names and stage values to HubSpot dealstage pick-list values. Stage probability and forecast category are re-applied per HubSpot pipeline settings.

Wyvern Magic activity records map to HubSpot engagements. Calls become HubSpot call engagements, emails become email engagements, meetings become meeting engagements, and notes become HubSpot notes. Original timestamps, owners, and parent-record links (contact, company, deal) are preserved. Any attachments linked to the activity are also transferred to HubSpot Files and associated back to the same parent record, maintaining a complete activity history.

Wyvern Magic custom fields map to HubSpot custom properties. We create the custom properties in your HubSpot portal before migration using the same field type (text, number, date, picklist, checkbox). If Wyvern Magic uses pick-list fields, we map values value-by-value into HubSpot pick-list options.

If Wyvern Magic has custom objects beyond the standard Contact/Company/Deal model, HubSpot Enterprise's custom objects provide a 1:1 destination. Custom object associations that use N:N relationships in Wyvern Magic may need HubSpot custom junction associations — we surface this in the pre-migration schema plan.

Wyvern Magic file attachments re-upload to HubSpot Files. Files are associated to their parent records (contact, company, deal) using HubSpot's file association API. File size limits apply per HubSpot's file storage policy. During re-upload, we preserve original file names and creation timestamps, and we handle any files exceeding HubSpot's size limit by splitting or compressing them before ingestion.

Wyvern Magic users resolve by email match against HubSpot users. FlitStack generates an owner-resolution report before migration — any Wyvern Magic owner without a matching HubSpot user email is flagged so your team can create HubSpot users or assign to a fallback owner before the migration runs.

Wyvern Magic workflows and automation rules do not migrate to HubSpot. They must be rebuilt using HubSpot's workflow builder. FlitStack exports your Wyvern Magic workflow definitions as a reference document for your HubSpot admin to use during rebuild. The exported file includes trigger conditions, action steps, and any conditional logic to aid in recreating equivalent automations in HubSpot's workflow engine.