CRM migration

Migrate from Wyvern Magic to Freshsales

Field-level mapping, validation, and rollback between Wyvern Magic and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

Wyvern Magic logo

Wyvern Magic

Source

Freshsales

Destination

Freshsales logo

Compatibility

90%

9 of 10

objects map 1:1 between Wyvern Magic and Freshsales.

Complexity

CModerate

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Wyvern Magic logo

Wyvern Magic

What's pushing teams away

  • Niche fit — Wyvern Magic is built around marketing-led publishing/events workflows; teams in horizontal SaaS sales find features overweight in some areas and underweight in others.
  • Limited public API documentation and developer community make integration with modern HRIS/marketing stacks slow.
  • Marketing footprint is small; reviewers cite limited online reference material and procurement-readiness documentation.
  • Reporting depth, while described as comprehensive, is structured around the publishing/sponsorship use case rather than horizontal SaaS metrics.
  • Modernization pace is slower than category leaders; UI/UX trails newer CRMs.

Choosing

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Wyvern Magic objects map to Freshsales

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

maps to

Freshsales

Contact

1:1
Fully supported

Wyvern 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

maps to

Freshsales

Account

1:1
Fully supported

Wyvern 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

maps to

Freshsales

Deal

1:1
Fully supported

Wyvern 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

maps to

Freshsales

Deal Pipeline

lossy
Fully supported

Wyvern 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

maps to

Freshsales

Lead

1:1
Fully supported

Wyvern 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

maps to

Freshsales

Email + Task

1:1
Fully supported

Wyvern 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

maps to

Freshsales

Call Log

1:1
Fully supported

Wyvern 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

maps to

Freshsales

Meeting

1:1
Fully supported

Wyvern 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

maps to

Freshsales

Note

1:1
Fully supported

Wyvern 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

maps to

Freshsales

User

1:1
Fully supported

Wyvern 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.

Gotchas + challenges

What specifically takes care here

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 logo

Wyvern Magic gotchas

Medium

Hierarchical calendar approval workflows don't map to flat calendars in modern CRMs

Medium

Sponsorship and event objects don't have standard equivalents in most CRMs

Low

Email metrics history is denormalized into contact records

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Wyvern Magic lacks a public API for direct extraction

    Wyvern Magic does not expose a public REST or GraphQL API for automated data extraction. All migration data must be extracted through Wyvern Magic's native export function (CSV or platform-native format), which requires manual initiation and may be limited by tenant-tier export caps on record count or frequency. We coordinate the export process with the customer's Wyvern Magic admin, validate the export completeness against record counts in the platform, and handle any file-encoding issues during transform. If the export is incomplete or missing fields, we flag the gap before any data moves to Freshsales.

  • Pipeline and stage names are tenant-configurable

    Wyvern Magic allows per-tenant pipeline and stage name customization, meaning there is no fixed stage name vocabulary to map from. We extract the active pipeline definition during scoping and recreate it as a Freshsales Deal Pipeline before migrating any deal records. Stage probabilities are extracted and mapped to Freshsales stage percentages. If Wyvern Magic uses multiple pipelines for different business units, we create corresponding Freshsales pipelines and assign deal records to the correct pipeline during migration. This configuration step must complete before deal record migration begins.

  • Workflows and automation rules do not migrate

    Wyvern Magic automation rules (workflow triggers, conditional actions, marketing automation sequences) are not migrated to Freshsales as code. Freshsales Workflows use a different trigger-action model (event-based or scheduled with conditions) and are configured through Freshsales Admin Settings. We deliver a written inventory of every active Wyvern Magic automation with its trigger, conditions, and actions, and a recommended Freshsales Workflow equivalent. The customer's admin rebuilds these post-migration. Post-migration, outgoing emails in Freshsales are disabled by default and must be re-enabled by Freshsales support or the admin.

  • File attachments may require a separate migration pass

    Wyvern Magic attachment storage configuration varies by tenant. Large file attachments stored in Wyvern Magic's file storage may need a separate file-migration pass after the record migration completes. We migrate file attachment references (URLs, file names, sizes) as part of the record migration. If the attachment storage is exportable as a zip or file share, we include it in scope; if it requires screen-scraping or manual download, we flag it for the customer to handle separately or as an additional pass.

Migration approach

Six steps for a successful Wyvern Magic to Freshsales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Wyvern Magic logo

Wyvern Magic

Source

Strengths

  • Event and sponsorship management as first-class CRM objects.
  • Marketing-led design with built-in campaign analytics overlay on contact behaviour.
  • Hierarchical shared calendar with approval workflows for sales-team coordination.
  • Sales diary tracking gives managers per-rep activity visibility.
  • UK domain expertise in subscription publishing and sponsorship workflows.

Weaknesses

  • Narrow vertical fit; horizontal SaaS sales teams find the data model awkward.
  • Limited public API and developer documentation.
  • Smaller reference community and procurement documentation.
  • Reporting structure is publishing/sponsorship-centric, not horizontal SaaS-centric.
  • Slower modernization pace than category leaders.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Moderate CRM migration. 5 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Wyvern Magic and Freshsales.

  • Object compatibility

    C

    5 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Wyvern Magic: Not publicly documented.

  • Data volume sensitivity

    B

    Wyvern Magic doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Wyvern Magic to Freshsales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Wyvern Magic to Freshsales data migrations

Answers to the questions buyers ask most during Wyvern Magic to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and four weeks for accounts under 15,000 Contacts and 3,000 Deals with a clean custom field schema and no multi-pipeline complexity. Migrations with multiple custom objects, large activity histories (over 200,000 engagement records), or multi-pipeline Deal structures requiring Freshsales pipeline and stage configuration move to five to eight weeks. Wyvern Magic's lack of a public API means export extraction time adds to the discovery and scoping phase relative to platforms with API access.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Wyvern Magic.
Land in Freshsales, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day