Migrate from NinjaPipe to Salesforce Sales Cloud

NinjaPipe Contacts map directly to Salesforce. If the customer's NinjaPipe data includes lead-type records (pre-qualified prospects without an associated Deal), we map those to Salesforce Lead. Contacts with at least one associated Deal map to Salesforce Contact attached to the migrated Account. We preserve all standard contact fields (name, email, phone, company, tags) and enumerate any custom fields during discovery, mapping each to a typed Salesforce custom field (text, number, date, picklist) before import. Tags on Contact migrate as a multi-select picklist or to Salesforce Topics depending on usage pattern.

NinjaPipe CRM-side Company records map to Salesforce Account. Domain from the CRM Company record becomes the Account Website field. Account is inserted before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. If the customer has Companies in both the CRM and Sales modules, we deduplicate by domain and create a single Account with a note flagging the dual origin for the customer's admin to reconcile.

Each NinjaPipe Pipeline (Kanban board) becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process. The Sales Process whitelists stage values and controls the stage dropdown for users. Stage colours from NinjaPipe are noted in the migration scope document for manual reapplication as Salesforce stage icons or page layout colour coding. We configure the Record Type and Sales Process in a Salesforce Sandbox before production migration.

NinjaPipe Deals attached to Pipeline Stages map to Salesforce Opportunities. Deal value (amount), stage assignment (pipeline_stage_id), owner (hubspot_owner_id equivalent), and close date migrate directly. Deals without a Pipeline assignment are held in a reconciliation queue for the customer to assign a Record Type and Sales Process before import. Custom fields on Deals enumerate and map to typed Salesforce custom fields. Closed-Lost and Closed-Won status migrate with the original timestamp preserved.

NinjaPipe Pipeline Stage names and ordering become Salesforce StageName values within the Sales Process created for that Pipeline. Stage probability percentages transfer to StageProbability. We round HubSpot probabilities to Salesforce's integer-requirement. The customer decides whether to use Salesforce's standard stage names (Prospecting, Qualification, etc.) or custom stage names matching NinjaPipe's labels; the migration preserves the original stage name as a custom field on Opportunity for reporting continuity.

NinjaPipe Tasks assigned to Contacts or Deals migrate to Salesforce Task. Title, description, due date, status (open/completed), and owner (resolved via email match to Salesforce User) transfer directly. Task ordering on the activity timeline is preserved by setting ActivityDate to the original NinjaPipe timestamp. Completed task timestamps are preserved as-is. NinjaPipe due-date sorting limitations on the source do not affect migration; the due_date field is a standard Salesforce field that supports sorting natively.

NinjaPipe Products from the Sales module catalog map to Salesforce Product2. Product name, SKU (product_code), price (unit_price), and description transfer. We handle the documented bulk import failure risk by batching Products in groups during extraction and logging which batches fail, retrying with sanitized values. Salesforce PricebookEntry records are created for the Standard Pricebook during import. The customer decides whether Products should be linked to Opportunities via Line Items post-migration or remain as a standalone catalog.

NinjaPipe Orders are manually entered in the Sales section with no linkage to CRM Deals. We migrate Order records as standalone objects. If the customer uses Salesforce Order Management (available from Sales Cloud Enterprise), Orders migrate to the standard Order object with Opportunity linkage created post-import. If Salesforce Order Management is not in scope, Orders migrate to a custom Order object (Order__c) with a lookup to Account and optional lookup to Opportunity for manual reconciliation. The lack of foreign key linkage in NinjaPipe is the governing constraint here: we cannot auto-link Orders to Deals without a source-side relationship to resolve.

NinjaPipe Automation Workflows (trigger-action rules on Contacts, Deals, or Tasks) do not migrate as code. We export the full rule logic: trigger type, conditions, action sequence, and any delay steps. We deliver a written Flow inventory document mapping each NinjaPipe Automation to its recommended Salesforce Flow equivalent (record-triggered, scheduled, or screen flow). The customer's admin or a Salesforce partner rebuilds the automations post-migration. Automations on the Sales module are documented as not available in NinjaPipe, which we note as a gap rather than a migration item.

NinjaPipe Form definitions and submission data do not migrate as a functional form. We export the form schema (field structure, field types, routing rules) and submission history. Submissions with Contact data map to Lead or Contact records enriched with form field values as custom properties. The form UI itself must be rebuilt in Salesforce; we document the original form structure to guide the admin in recreating it as a Salesforce Web-to-Lead form or Experience Cloud form. File attachment fields on NinjaPipe forms have no direct Salesforce equivalent and are flagged as a gap.

NinjaPipe Booking Pages (appointment scheduling tools) migrate as configuration documentation: page settings, availability windows, and booking-to-contact associations. Salesforce Scheduler (available from Sales Cloud Enterprise with Salesforce Maps) or a third-party scheduling integration replaces booking pages. We preserve the booking data (scheduled appointments as Event records) during migration but do not configure Salesforce Scheduler; that is handled by the customer's admin post-migration.

Custom fields defined on NinjaPipe Contacts, Deals, and Pipeline Stages are enumerated during discovery and mapped to typed Salesforce custom fields before any record import. Field types translate as: text to Text, number to Number, date to Date, dropdown to Picklist, checkbox to Checkbox, email to Email. Lookup fields to other NinjaPipe objects (e.g., a custom Deal field referencing a Contact) resolve to the equivalent Salesforce lookup at migration time after parent records are inserted.

NinjaPipe Databins (named data stores for webhook payloads and custom data logic) export as flat JSON objects. We attach these as a JSON file to the related CRM record (Contact or Deal) via Salesforce ContentDocument, or pre-create a custom Databin__c object in Salesforce if the customer needs structured access to this data post-migration. Databin schema definitions are documented in the migration scope for the admin to configure the destination object.