Migrate your NinjaPipe data

Contacts are the core CRM object in NinjaPipe. Standard fields (name, email, phone, company, tags) map 1:1 to most destination CRMs. Custom fields on contacts are preserved as custom properties during migration. Owner assignment is carried over where the destination supports user-level record ownership.

NinjaPipe Pipelines are Kanban boards representing sales processes. We migrate pipeline names, stage names, stage order, and stage colours. Each Pipeline Stage becomes a status column or stage in the destination. The association between Deals and their Pipeline Stages is preserved throughout the migration.

Deals are attached to Pipeline Stages and carry fields including deal value, contact association, owner, and custom fields. We map deal values and stage assignments directly. Deals without a Pipeline assignment land as unqualified leads in the destination unless a default pipeline is configured during scoping.

NinjaPipe Automations are trigger-action rules scoped to Contacts, Deals, or Tasks. We export the full rule logic (trigger type, conditions, action sequence) and attempt to reconstruct equivalent rules in the destination where it supports workflow automation. Complex multi-step sequences or platform-specific actions (e.g. NinjaPipe-specific integrations) may require manual recreation post-migration.

NinjaPipe Invoice records carry line items, totals, status, and contact association. We migrate Invoice metadata but not the financial ledger entries themselves. If the destination is a dedicated accounting platform, line items are mapped to Products and Invoice totals to the corresponding invoice object; otherwise invoices land as linked records on the Contact.

NinjaPipe Products are a separate catalog used in the disconnected Sales module. They carry name, price, description, and SKU. Product import failures (execution failure error) are documented gotchas. We retry product imports with batched payloads and log any records that fail for manual recovery. Products without SKUs receive auto-generated identifiers.

Orders are manually entered in the Sales section with no connection to Deals, Quotes, or Invoices in the CRM. We migrate Orders as standalone records but cannot auto-link them to pipeline Deals without a foreign key in NinjaPipe's data model. Customers who want Orders attached to Deals must perform manual association post-import.

NinjaPipe Forms capture lead data and can route submissions to Contacts or Pipelines. We migrate Form definitions and field structure. Submission history is migrated as Contact records enriched with form-source metadata. Form routing rules (which pipeline/stage a submission lands in) are preserved where the destination supports equivalent routing logic.

Booking Pages are appointment scheduling tools scoped to contacts or deals. We migrate page settings, availability windows, and booking-to-contact associations. If the destination does not have a native booking feature, booking pages are migrated as Calendar Events linked to the corresponding contact record.

Tasks in NinjaPipe are assigned to Contacts or Deals, carry due dates, statuses, and owners. Task titles, descriptions, due dates, and assignees map directly. Completed vs. open status is preserved. Subtasks are migrated as linked child tasks where the destination schema supports task hierarchies.

Custom fields defined on Contacts, Deals, and Pipeline Stages are enumerated during discovery and mapped to equivalent custom properties in the destination. Field type translation (date, number, dropdown, multi-select) is handled explicitly. Fields with no equivalent type in the destination are migrated as text with a data-type annotation.

NinjaPipe Client Portals are white-label, branded portals for external clients to view their records and documents. We do not migrate Client Portal configurations because they depend on branding assets, domain CNAME settings, and permission templates that cannot be reliably reconstructed outside NinjaPipe. Portal-accessible records (contacts, invoices) are migrated as standard records.

Whiteboards are visual collaboration canvases for brainstorming and planning. They store spatial layout data, shapes, and freeform text that cannot be reliably mapped to any standard CRM object. We do not migrate Whiteboard content.

Databins are named data stores used for webhook payloads, temporary storage, and custom data logic. We export Databin schemas and any persisted records as flat JSON objects attached to the associated Contact or Deal. Migration of active webhook endpoints requires manual reconfiguration in the destination.