CRM migration
Field-level mapping, validation, and rollback between Wyvern Magic and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Wyvern Magic
Source
Freshsales
Destination
Compatibility
9 of 10
objects map 1:1 between Wyvern Magic and Freshsales.
Complexity
CModerate
Timeline
2-4 weeks
Overview
Moving from Wyvern Magic to Freshsales requires resolving a structural export constraint first: Wyvern Magic does not provide a public API for direct data extraction. We extract data through Wyvern Magic's native export capabilities, transform the exported records into Freshsales-compatible formats, and load via Freshsales REST API with batch chunking. The migration covers Contacts, Companies, Deals, Leads, Activity records (calls, emails, meetings, tasks, notes), Custom Objects, and User/Owner assignments. Pipeline definitions are extracted from Wyvern Magic tenant configuration and recreated as Freshsales Deal pipelines before record migration begins. Tags, custom properties, and lifecycle stage assignments are preserved as Freshsales custom fields or label associations. Workflows, automations, and reporting configurations do not migrate as code; we deliver a written inventory for the customer's admin to rebuild in Freshsales Workflows.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Wyvern Magic object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Wyvern Magic
Contact
Freshsales
Contact
1:1Wyvern Magic Contact records map 1:1 to Freshsales Contact. Standard fields (name, email, phone, address) transfer directly. We apply a type-inference step to map any Wyvern Magic custom contact properties to Freshsales custom fields, assigning the correct field type (text, number, date, picklist) during the transform phase. Contact records are loaded before Deals so that account and contact lookups are satisfied at insert time.
Wyvern Magic
Company
Freshsales
Account
1:1Wyvern Magic Company records map to Freshsales Account. The company domain and industry fields transfer directly. We use the Account Name as the dedupe key during Freshsales import. Account is created before Contact import so that the primary_contact_id relationship and any account-contact associations are valid at insert.
Wyvern Magic
Deal
Freshsales
Deal
1:1Wyvern Magic Deal records map to Freshsales Deal. Pipeline and stage names are tenant-configurable in Wyvern Magic; we extract the active pipeline definition first, create the corresponding Freshsales Deal pipeline and stage values, then map deal records into the correct stage. Deal amount, probability, close date, owner, and associated contact/account references transfer directly. Closed-Lost and Closed-Won reason fields from Wyvern Magic custom properties map to Freshsales Deal loss_reason and custom fields.
Wyvern Magic
Pipeline
Freshsales
Deal Pipeline
lossyWyvern Magic pipeline definitions (stages, probabilities, stage order) are extracted separately from deal records during scoping. Each Wyvern Magic pipeline becomes a Freshsales Deal Pipeline with matching stage names and probability percentages. Stage order is preserved. If the customer has multiple Wyvern Magic pipelines, we create corresponding Freshsales pipelines and map deal records to the appropriate pipeline during migration.
Wyvern Magic
Lead
Freshsales
Lead
1:1Wyvern Magic Lead records map to Freshsales Lead. Lead source, status, rating, and any custom scoring fields transfer to Freshsales Lead fields. If the customer uses Wyvern Magic lifecycle stage assignments on leads, we preserve them in a custom field for segmentation after migration. Lead-to-Contact conversion is handled post-migration by the customer's admin using Freshsales native conversion action.
Wyvern Magic
Activity: Email
Freshsales
Email + Task
1:1Wyvern Magic email engagements map to Freshsales Email records linked to an Activity Task. Email subject, body, direction (sent/received), timestamp, and recipient data transfer. The associated Contact or Lead WhoId and the related Account or Deal WhatId are resolved via email-address lookup and parent-record resolution at migration time. Email activity timeline ordering is preserved by ActivityDate.
Wyvern Magic
Activity: Call
Freshsales
Call Log
1:1Wyvern Magic call engagements map to Freshsales Call Log records with call disposition, duration, outcome, and timestamp preserved. Call recording URLs stored as custom fields transfer to Freshsales call_log custom fields if available, or remain as notes on the linked Contact or Deal. Owner assignment migrates by resolving the Wyvern Magic owner reference to the Freshsales User via email match.
Wyvern Magic
Activity: Meeting
Freshsales
Meeting
1:1Wyvern Magic meeting engagements map to Freshsales Meeting records with start time, end time, location, title, and attendee data preserved. Attendee emails are linked to Freshsales Contact or Lead records via email lookup. Meeting notes and description text transfer directly. Owner assignment migrates by resolving Wyvern Magic owner reference to Freshsales User.
Wyvern Magic
Activity: Note
Freshsales
Note
1:1Wyvern Magic notes attached to contacts, deals, or companies map to Freshsales Notes linked to the parent record via ContentDocumentLink. Note body text migrates with timestamp preserved. If the note contains file attachments, we migrate them as separate file records with a reference link back to the note.
Wyvern Magic
User/Owner
Freshsales
User
1:1Wyvern Magic Owner records are mapped to Freshsales User by email address. We extract all distinct owner emails referenced on Contacts, Companies, Deals, and Activity records. Any Wyvern Magic owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active owner status is preserved; inactive Wyvern Magic owners are flagged for admin decision on Freshsales user activation.
| Wyvern Magic | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Deal Pipelinelossy | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Activity: Email | Email + Task1:1 | Fully supported | |
| Activity: Call | Call Log1:1 | Fully supported | |
| Activity: Meeting | Meeting1:1 | Fully supported | |
| Activity: Note | Note1:1 | Fully supported | |
| User/Owner | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Wyvern Magic gotchas
Hierarchical calendar approval workflows don't map to flat calendars in modern CRMs
Sponsorship and event objects don't have standard equivalents in most CRMs
Email metrics history is denormalized into contact records
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Scoping and Wyvern Magic export coordination
We audit the Wyvern Magic tenant for record counts across Contacts, Companies, Deals, Leads, Activities, and Custom Objects. We identify the export method (native CSV export, platform download), validate record completeness, and flag any tier-gated objects that require admin-level access. We map Wyvern Magic custom properties and pipeline configurations, then document the Freshsales destination tier recommendation based on the customer's object and user count requirements.
Schema design in Freshsales
We configure the Freshsales destination schema: custom fields created to receive Wyvern Magic custom properties with correct types (text, number, date, picklist), Deal Pipelines and stages created to match Wyvern Magic pipeline definitions, Record Types assigned per pipeline if applicable, and custom fields for lifecycle stage, owner references, and attachment URLs. Schema is deployed to Freshsales via API or admin console before any record import begins.
Data export and transform
We extract data from Wyvern Magic using the platform's native export mechanism, validating record counts against platform UI totals. We transform the exported data into Freshsales-compatible CSV and JSON formats, applying field-type mapping, date format normalization, and owner email resolution. Any Wyvern Magic-specific enumerated values (lifecycle stages, lead statuses) are mapped to Freshsales picklist values or preserved as custom field text if no matching picklist exists.
Owner reconciliation and User provisioning
We extract all distinct Wyvern Magic owner email addresses and match them against the Freshsales destination User table. Owners without a matching Freshsales User are listed for the customer's admin to provision. We resolve Owner references on Contacts, Companies, Deals, and Activities to the corresponding Freshsales User ID before record insert to avoid orphaned records.
Record migration in dependency order
We run record migration in dependency order: Accounts (from Wyvern Magic Companies), Contacts (with AccountId resolved), Leads, Deals (with pipeline, stage, and AccountId resolved), Activity history (calls, emails, meetings, tasks, notes via Freshsales Bulk API with chunking and rate-limit handling). Each phase emits a row-count reconciliation report. We flag any records that fail import due to validation rules or missing required fields for admin resolution before the next phase.
Cutover, validation, and automation inventory handoff
We freeze Wyvern Magic writes during the cutover window, run a final delta migration of any records modified during the migration period, then enable Freshsales as the system of record. We deliver the automation inventory document listing every Wyvern Magic workflow and automation rule with Freshsales Workflow equivalents for the admin to rebuild. We support a one-week post-migration validation window where we resolve reconciliation issues raised by the customer's team.
Platform deep dives
Wyvern Magic
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 5 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Wyvern Magic and Freshsales.
Object compatibility
5 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Wyvern Magic: Not publicly documented.
Data volume sensitivity
Wyvern Magic doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Wyvern Magic to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Wyvern Magic to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Wyvern Magic
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.