Migrate from SalesNexus to Salesforce Sales Cloud

SalesNexus Contact records map to Salesforce Lead for unqualified prospects and Salesforce Contact for qualified buyers, following the same lifecycle model as HubSpot. We compute the split using the SalesNexus contact_status and tier fields if present, otherwise we map all Contacts to Salesforce Lead for the admin to reclassify post-migration. Original SalesNexus contact tier and enrichment data migrate to custom fields tier__c and enrichment_source__c on both Lead and Contact for audit continuity.

SalesNexus Company records map directly to Salesforce Account. Company ID from SalesNexus is preserved in a custom field sn_company_id__c for dedupe and cross-reference. The Account is created before any Contact import so that the AccountId lookup is satisfied at Contact insert time.

SalesNexus Pipelines (up to 10 on Starter, unlimited on Enterprise) map to Salesforce Opportunity Record Types, each paired with a Sales Process that scopes the available StageName values. We query the SalesNexus pipeline list via API, then pre-create the Record Types in the destination org before any Opportunity data is imported. Pipeline names become Record Type labels, and the first Pipeline defaults to the standard Opportunity object if no custom Record Type is needed.

SalesNexus Pipeline Stages map to Salesforce Opportunity Stage values. Stage order is preserved as the StageName sequence, and probability percentages migrate to StageProbability. If the destination org already has stages configured, we map by best-match name rather than creating duplicates. Stage-level probability defaults migrate as integer percentages.

SalesNexus Tasks map to Salesforce Task with Status, Priority, ActivityDate, and Subject preserved. Owner assignment migrates via email-to-User resolution. Completed tasks retain their completion timestamp; open tasks are migrated with their original due dates.

SalesNexus Users referenced as record owners are resolved by email against the destination Salesforce org's User table. Any User without a match is placed in a reconciliation queue for the customer's admin to provision before the production migration phase begins. Inactive SalesNexus users map to inactive Salesforce Users where historical assignment must be preserved.

SalesNexus custom fields on Contacts are identified via the get-all-fields endpoint using integer field IDs. We retrieve the full field schema (label, type, options), then create matching custom fields in Salesforce using the standard __c naming convention. Field types are mapped: text fields to Text, number fields to Number, date fields to Date, and picklist fields to Picklist. The original SalesNexus field ID is stored in a custom field sn_field_id__c for reference.

SalesNexus custom fields on Companies are handled identically to Contact custom fields: schema extracted via get-all-fields, Salesforce custom fields pre-created in the destination org before Account import begins. Lookup relationships between custom fields and other objects are resolved using the parent-record lookup pattern.

SalesNexus email template bodies and subject lines are exported as text artifacts. Merge field syntax differs between platforms, and we convert common patterns (e.g., {{contact.name}} to {!Contact.Name}) during export. Because email templates in Salesforce are stored as Salesforce Content objects with different rendering contexts, we deliver a template conversion report; the customer's admin rebuilds templates in Salesforce Email Templates or a third-party email tool.

SalesNexus email archival (unlimited on all plans) exports subject, body, date, and direction (sent/received). HTML email bodies are converted to plain text or preserved as HTML depending on the destination org's email rendering settings. Emails are linked to the parent Contact or Company via the WhoId and WhatId fields on Task. Email archival links pointing to the SalesNexus platform are preserved as URL text but the links become inactive after migration unless the customer maintains a SalesNexus read-only license.

SalesNexus call recording URLs and transcription text are exported and attached to Salesforce Tasks with TaskSubtype = Call. Binary audio files are not downloadable via the SalesNexus API, so only the URL reference and transcription text migrate. If the customer has an active SalesNexus license post-migration, the URL remains accessible; otherwise it becomes a broken link and should be replaced by a call recording re-upload to a cloud storage solution.

SalesNexus drip sequences are not accessible via API, but enrolled contact IDs, sequence names, and enrollment dates are retrievable. We export this enrollment data into a Salesforce custom object (Drip_Sequence_Enrollment__c) or as a CSV inventory for the customer to use as a rebuild reference. The sequence audit report lists each active sequence, the number of enrolled contacts, and the sequence trigger type (date-based, action-based) as described in the source platform. Rebuilding the actual automation logic in Salesforce Flow is a manual step for the customer's admin.

SalesNexus form schemas (field configurations and webhook/post URLs) are exported as metadata. The form embedding code (iframe) is platform-specific and cannot be imported into Salesforce. We deliver a form schema inventory listing every active form, its field set, and its submission destination so the admin can recreate forms using Salesforce Web-to-Lead, Experience Cloud, or a third-party form tool like FormAssembly or Formstack.

SalesNexus dashboard configurations (up to 20 on Starter, unlimited on Enterprise) are exported as metadata describing the report source, chart type, and filter set. Salesforce reports use a different object model (Reports and Dashboards in Analytics Cloud), so dashboards cannot be imported as working artifacts. We deliver a dashboard inventory document mapping each SalesNexus dashboard to its equivalent Salesforce report type and chart configuration for the admin to rebuild.