Migrate from Visionary to Freshsales

Visionary contacts that have not been qualified map to Freshsales Leads. The Freshsales Lead object stores pre‑qualification data such as source, status, and score before conversion to a Contact. Owner resolution occurs by matching the Visionary owner email to a Freshsales user; unmatched owners are flagged so your team can provision Freshsales access or assign a fallback owner before the load.

Visionary contacts that are recognized customers or have passed an initial qualification step route to Freshsales Contacts. Each Contact requires an AccountId lookup, so Visionary embedded company data must first be decomposed into Freshsales Account records. Owner resolution matches the Visionary owner email to a Freshsales user; any unmatched contacts are flagged for provisioning before the load. Duplicate detection by email prevents multiple Contact records for the same address.

Visionary stores company data either embedded in contact records or as lightweight name/address entries. FlitStack extracts these into Freshsales Account objects, preserving industry classification, employee count, annual revenue, and website. Parent‑child hierarchies in Visionary map to Freshsales Account.ParentId; circular references are flagged for manual resolution. Missing firmographic fields are left blank and can be enriched post‑migration using Freshsales built‑in tools.

Visionary deal records map to Freshsales Opportunities. The deal name becomes the Opportunity Name, while amount, close date, and stage name transfer directly. Pipeline association in Visionary is represented as the Freshsales Pipeline field, and stage names are translated using the value‑mapping table, with forecast category assignment. OwnerId is resolved by matching the Visionary owner email to a Freshsales user; deal notes are stored in the Opportunity Description field.

Each Visionary pipeline is converted into a Freshsales Sales Process, creating a dedicated stage pick‑list for that pipeline in Freshsales. Stage names are mapped value‑by‑value, preserving the original sequence and applying any custom stage probabilities or forecast categories you have defined. If Visionary contains multiple pipelines, each one results in a separate Freshsales Sales Process, allowing you to assign default owners or territories after migration.

Visionary call logs map to Freshsales Tasks with Type='Call', email records map to Tasks with Type='Email', and meeting records map to Events with start and end times preserved. Each activity is linked to its parent record (Lead, Contact, Account, or Opportunity) using the Visionary ID cross‑reference so context appears in Freshsales timelines. Original timestamps and owner attribution are retained.

Visionary notes are imported as Freshsales Notes attached to the appropriate parent record (Lead, Contact, Account, or Opportunity) using the Visionary note ID for cross‑reference. Rich‑text formatting, including any embedded images or links, is preserved where Visionary supports it; plain‑text fallback is applied for simpler note formats. If a Visionary note contains attachments, those files are migrated as Freshsales Files and linked to the note record.

Visionary custom fields on contacts are created as Freshsales custom fields on both Contact and Lead objects (for parity during lead-conversion scenarios). Field type compatibility is validated: pick-list fields require matching value sets, numeric fields map to Freshsales Number type.

Visionary owner IDs are resolved against Freshsales users by matching the email address stored in the owner record to the Freshsales user email. The resolved Freshsales user ID populates the OwnerId field on the migrated record, ensuring assignment and visibility. Any unmatched owners are flagged during pre‑flight; your team can either provision Freshsales accounts for those users or assign a fallback owner before the data load begins, preventing orphaned records.

Visionary file attachments on records are downloaded and re‑uploaded to Freshsales Files, then linked to the corresponding record (Lead, Contact, Account, or Opportunity) using the Visionary attachment ID for reference. Freshsales enforces a 25 MB per‑file limit; files exceeding this threshold are split or flagged for manual handling. Inline images embedded in notes are extracted, re‑hosted as Freshsales Files, and inserted back into the note body to preserve visual context.

Visionary workflows, sequences, and automation rules do not migrate — they execute within Visionary's engine and have no Freshsales equivalent. FlitStack exports workflow definitions as a rebuild reference document for your Freshsales admin to recreate in Workflows and Sequences post-migration.

Visionary reports and dashboards are not migrated because each platform stores report definitions in its own engine. The underlying data—contacts, accounts, opportunities, and activities—does migrate, so Freshsales native reports can query the same dataset after migration. FlitStack exports Visionary report layouts and filter criteria as a reference document, and your team rebuilds those reports using Freshsales's reporting builder, leveraging Freshsales dashboards, widgets, and email delivery to replicate the original insights.