Migrate from NextCRM to Salesforce Sales Cloud

NextCRM Contact records map to Salesforce Lead or Contact depending on business qualification status. Contacts with no associated Deal and no revenue attribution data map to Salesforce Lead. Contacts attached to a Deal or tagged with list membership indicating a sales-qualified status map to Salesforce Contact linked to an Account. We preserve the original NextCRM contact ID in a custom field nextcrm_id__c on both Lead and Contact for cross-reference. Tag assignments transfer as a custom multi-select picklist nextcrm_tags__c for segmentation continuity during the transition window.

NextCRM tags transfer as a custom multi-select picklist field on the Lead or Contact record (nextcrm_tags__c) if the tag vocabulary is small (under 150 distinct tags). If the vocabulary exceeds Salesforce's 500-value multi-select limit or tags represent audience segments with campaign membership behavior, we map tags to Salesforce Campaigns with CampaignMember records linking Contacts and Leads. The customer chooses the strategy during scoping based on their segmentation reporting needs.

NextCRM Lists and Advanced Segmentation rules do not have a direct Salesforce equivalent because Salesforce stores segmentation logic in Campaigns, Reports, and List Views rather than as reusable dynamic segments. We transfer list membership as Salesforce Campaign records with all current members enrolled as CampaignMembers. For dynamic segmentation rules (rules that auto-update based on contact properties), we deliver a written inventory of each segment's logic so the customer's admin can rebuild them as Salesforce Reports with dynamic filters or Salesforce Flow-based audience actions.

NextCRM custom field definitions and their stored values migrate to Salesforce custom fields on the Lead, Contact, or Account object. We map field types to Salesforce equivalents: text to Text(255), number to Number, date to Date, checkbox to Checkbox, dropdown to Picklist or Multi-Select Picklist. The destination custom fields are pre-created via Salesforce metadata API before any data import. If NextCRM stores data in JSON-encoded custom fields (common for WordPress plugin serialization), we parse and flatten the JSON into separate Salesforce fields during the transform phase.

The open-source nextcrm-app includes a Companies module that maps to Salesforce Account. We extract company records via direct PostgreSQL query, map the company_name to Account Name, company_domain to Website, and any billing address fields to the Account Address compound field. If NextCRM companies lack a dedicated API export path, we provide a SQL query template for the customer's database admin to run against their PostgreSQL instance.

The open-source nextcrm-app stores Deals with line items, tax engine data, and deal stage. These map to Salesforce Opportunity with OpportunityLineItem. We extract deal records, map deal_stage to a Salesforce StageName that we pre-configure in the destination org's Sales Process, and resolve the parent company reference to an AccountId. Tax and discount data transfer to custom Opportunity fields because Salesforce standard Opportunity does not include a native tax engine.

The nextcrm-app invoicing module (Invoice, Credit Note, Proforma, Receipt) does not map to a Salesforce standard object without Financial Services Cloud. We migrate invoice metadata (invoice number, series, date, line items, totals, tax amounts) into a custom Invoice__c object with InvoiceLine__c as a child. We flag whether the customer has or will acquire Financial Services Cloud during scoping so that the schema design accommodates a future Financial Services Cloud integration without a second migration.

Open-source project records (project name, status, task assignments) migrate to a custom Project__c object with Task__c as a child. We do not migrate project data into Salesforce's native task system because Salesforce Tasks are activity records tied to the activity timeline rather than a standalone project management structure. If the customer uses a third-party project management app from the AppExchange (Project Management for Salesforce, Asana, or Monday.com), we design the schema to support a later integration phase.

NextCRM campaign records transfer to Salesforce Campaign. Campaign name, audience (linked contact list), status, and scheduled send date migrate. Active campaign sends must be paused during migration; we preserve campaign structure and audience membership so the customer can re-create and resume sends in Salesforce from the original audience list. We flag any NextCRM campaign with an in-progress send in the migration report for the customer's marketing team to handle manually.

NextCRM document storage metadata (filename, file reference, linked record type, linked record ID) migrates to Salesforce ContentDocument and ContentDocumentLink. We do not migrate binary file storage; we transfer the file reference URL and create a ContentDocument record pointing to that URL. If files are stored locally within the WordPress instance rather than externally, the customer's admin must configure a document management solution (Salesforce Files, Google Drive integration, or SharePoint) before migration completes.

NextCRM owner records map to Salesforce User by email match. We extract every distinct owner referenced on Contact, Company, Deal, and Engagement records and match by email against the Salesforce destination org's User table. Any NextCRM owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner records without an email are flagged for manual mapping.

NextCRM Visual Automation Builder workflows are WordPress-plugin-native and cannot be exported as transferable data. We document the structure of every active workflow during the extraction phase: trigger type (form submit, tag added, date-based), condition branches, action sequence (email send, tag apply, field update, delay), and any active campaign references. This documentation is delivered as a written inventory with recommended Salesforce Flow equivalents so the customer's Salesforce admin rebuilds them post-migration. Workflows remain active on NextCRM during the cutover window for a phased transition.