Migrate your SalesNexus data

The primary CRM record in SalesNexus. All plans support contact creation, custom fields, enrichment data, and email history. We export contacts with their field IDs from the get-all-fields endpoint and map them to the destination Contact schema 1:1. Contact tier limits (1000 free, 5000 Starter, higher on Enterprise) must be validated before migration to avoid plan upgrades mid-project.

Company records in SalesNexus are standard objects linked to contacts via a company field. We export companies independently and then link them to imported contacts. No special handling required.

SalesNexus supports multiple named Pipelines (3 on free, 10 on Starter). Each pipeline contains ordered Pipeline Stages. We export the full pipeline schema and stage order, then recreate it in the destination CRM using the native pipeline/stage object model.

Stages are ordered integers within a pipeline. We preserve stage names, order, and probability defaults. If the destination CRM uses a different stage model (e.g., HubSpot deal stages), we map them by ordinal position and name.

Tasks are standard CRM tasks with due dates, assignees, and completion status. We export open and completed tasks, preserving the owner assignment via user email mapping.

SalesNexus stores email templates with merge fields and HTML content. We export template bodies and subject lines. Merge field syntax differs between platforms; we convert common patterns (e.g., {{contact.first_name}}) to destination-compatible tokens during import.

Drip automation sequences are stored server-side and are not accessible via the public API. We can export the list of active contacts enrolled in a sequence and the sequence name, but the workflow logic itself (triggers, delays, conditions) must be manually rebuilt at the destination. This is explicitly a manual-recreation item.

SalesNexus allows custom fields on Contacts and Companies identified by integer field IDs. We retrieve the full field schema via get-all-fields, export field labels and types, then map each to destination custom fields. Custom field types (dropdown, text, date) must be preserved to avoid data corruption.

Tasks and records are assigned to users by email. We export the user list and map by email to destination users. If a destination user does not exist, we assign to a default owner and flag for review.

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 API; we flag the link and advise customers to download recordings manually if needed.

All plans include unlimited email archival. We export email subject, body, date, and direction (sent/received). The email body is exported as HTML; we convert to plain text for CRMs that do not render HTML emails inline.

Nexi AI features (AI Email Assistant, AI Meeting Notes, Smart Recommendations) are platform-native and do not expose exported data. We export any Nexi-generated content stored as contact or activity notes, but the AI model outputs themselves cannot be migrated.

Forms are stored as objects with field configurations and webhook/post URLs. We export form schema and submission history. Form embeddings (iframe codes) are platform-specific and must be recreated in the destination.

SalesNexus supports up to 10 personalized boards and 20 dashboards depending on the plan. We export report configurations as metadata. Because report definitions are structured differently across CRMs, we recommend manual recreation guided by exported screenshots and notes rather than automated import.