Migrate from SalesNexus to Freshsales

SalesNexus Contact records map to Freshsales Lead or Contact depending on qualification status. Because SalesNexus has no separate Lead object, all Contacts must be evaluated for Freshsales placement: unqualified prospects land as Freshsales Lead; qualified contacts attached to a Company land as Freshsales Contact with Account association. We apply the split rule during scoping using the SalesNexus contact status field and pipeline enrollment, preserve the original SalesNexus contact record ID in a custom field for audit, and configure the Freshsales lead conversion field map (Admin Settings > Leads Module > Field Mapping) before migration so that converted leads create both Account and Contact in the destination.

SalesNexus Company records map directly to Freshsales Account. The Company name becomes the Account Name, website URL maps to the Account Website field, and industry classification maps to the Industry picklist where values align. Account is created before any Contact import so that the lookup relationship is satisfied at Contact insert. Companies without a matching SalesNexus contact receive a standalone Account import.

SalesNexus Pipelines (up to 3 on Free, 10 on Starter, unlimited on Team and Enterprise) map to Freshsales Deal Pipelines. Each SalesNexus pipeline name and stage order migrates as a Freshsales pipeline with named stages and default probabilities. If the destination Freshsales plan supports multiple pipelines, we recreate the full pipeline schema; if not, we consolidate into a single primary pipeline and flag the remainder for the customer's admin to configure post-migration.

SalesNexus pipeline stages are ordered integer values with probability defaults. We map each stage to a Freshsales deal stage with the equivalent probability value and stage name. Stage mapping preserves the deal progression logic by matching the SalesNexus stage index to the corresponding Freshsales stage position within the target pipeline.

SalesNexus Tasks (open and completed) migrate to Freshsales Tasks with subject, due date, status, priority, and owner assignment preserved. Task owner assignment resolves via email mapping from the SalesNexus user list to the Freshsales User table. Any SalesNexus user without a matching Freshsales User is flagged for the admin to provision before the task import phase begins.

SalesNexus custom fields on Contacts and Companies (identified by integer field IDs from the get-all-fields endpoint) map to Freshsales custom fields on the corresponding object. We retrieve the full SalesNexus field schema during discovery, export field labels and data types, then create matching Freshsales custom fields in Admin Settings before import. Field type mapping includes text-to-text, date-to-date, number-to-number, and picklist-to-picklist. Multi-select picklists in SalesNexus map to Freshsales multi-select picklists.

SalesNexus stores email templates with HTML content and merge fields. We export template bodies and subject lines. Merge field syntax differs between platforms; SalesNexus uses {{field_name}} patterns that we convert to Freshsales template variable format during export. HTML template structure is preserved and imported as a Freshsales email template.

SalesNexus unlimited email archival exports email subject, body (as HTML), date, direction (sent/received), and recipient. HTML email bodies are preserved for Freshsales instances that render HTML; plain-text fallback is generated for compatibility. Each email attaches to the corresponding Contact record via the Freshsales Activity timeline. Email association uses the recipient address to match against imported Contacts.

SalesNexus stores call recordings and transcriptions linked to Contact Activity records. We export the transcription text and a URL reference to the recording. Binary audio files are not downloadable via the SalesNexus public API, so the recording URL reference migrates as a link on the Freshsales activity record. Transcription text migrates as activity notes in Freshsales.

SalesNexus drip automation sequences are not exportable via API. We export the list of active contacts enrolled in each sequence, the sequence name, and enrollment dates. This enrollment data migrates as a Contact custom field (e.g., drip_sequence_enrolled__c with the sequence name as value) so the customer's admin has the enrollment history and can use it as a trigger condition in Freshsales Workflows. The workflow trigger logic, delay rules, and conditional branches must be rebuilt manually in Freshsales; we provide a sequence audit report as part of the handoff package.