Migrate from NinjaPipe to Pipedrive

NinjaPipe Contacts map to Pipedrive Person records. Standard fields (name, email, phone, company, tags) migrate directly. We resolve the company association by creating a corresponding Pipedrive Organization record and linking it via the Person's org_id. Custom fields on NinjaPipe Contacts enumerate during discovery and map to Pipedrive custom Person fields, with type translation applied for date, number, and dropdown fields. Duplicate detection uses email as the primary dedupe key.

NinjaPipe's Company field on Contact (or any standalone company reference) maps to Pipedrive Organization. In NinjaPipe, Company is a field on Contact rather than a separate object; we extract unique company name values during transformation and create Organization records before Person import so that the org_id lookup is satisfied at insert time. Website, address, and custom company fields migrate to Organization custom fields.

NinjaPipe Deals map to Pipedrive Deals with the pipeline stage mapping handled in the Pipeline Stage object step. Deal value, contact association (via Person), owner, expected close date, and custom deal fields migrate directly. We resolve the Person association by matching on email or name after Person records are confirmed in Pipedrive. Deals without a linked Pipeline Stage import as open Deals in the first Pipedrive stage.

NinjaPipe Pipelines (Kanban boards) map to Pipedrive Pipelines. We create Pipedrive Pipelines during schema setup using the pipeline name from NinjaPipe. Stage count and stage order are preserved. Pipeline-level settings (deal probability calculation, mandatory fields) are noted for manual configuration post-import.

NinjaPipe Pipeline Stages map to Pipedrive Pipeline Stages in the same order. Stage name and color migrate. Stage probability percentages from NinjaPipe map to Pipedrive stage probabilities. We configure the stage order within each Pipeline before Deals are imported so that stage assignments on Deal records resolve correctly.

NinjaPipe Tasks map to Pipedrive Activities with type set to Task. Due date, title, description, owner (resolved via email match to Pipedrive User), and completed vs. open status migrate. Activity is linked to the parent Person or Organization via the activity's person_id and org_id. We preserve historical activity timestamps so the Pipedrive timeline reflects the original NinjaPipe dates.

NinjaPipe Automation Workflows (trigger-action rules on Contacts, Deals, or Tasks) are exported as a written inventory: trigger type, conditions, action sequence, and recommended Pipedrive automation equivalent. Pipedrive's automation canvas (Workflows in Advanced tier and above, or Power Automate integration for Essential) uses a different rule model. We do not migrate automations as code. The inventory document is delivered to the customer's admin for rebuild.

NinjaPipe Form definitions (field structure, routing rules, submission-to-contact mapping) are exported as a written schema with field types and validation rules. Pipedrive has limited native form capability; complex intake forms require rebuild in an external tool (Typeform, Gravity Forms) with webhook integration to Pipedrive. We document the form schema so the customer's admin can recreate it in their preferred tool.

NinjaPipe Orders live in the disconnected Sales module with no foreign key linking them to CRM Deals. We treat Orders as a separate export stream and advise during scoping whether they should be merged into existing Deal notes (if a match can be determined by contact and date proximity) or imported as standalone Note records attached to the Person. The customer chooses the merge strategy before import begins.

NinjaPipe Products (name, price, description, SKU) from both the CRM product catalog and the Sales module catalog map to Pipedrive Products. NinjaPipe product import failures (generic execution error) are mitigated by batch processing in groups of 10-20 during outbound extraction and pre-validation against known field constraints. Products can be linked to Deals in Pipedrive via the Product-linked Deal item model.

NinjaPipe Invoices (line items, totals, status, contact) migrate as Note records or as custom fields on the linked Deal or Person in Pipedrive. Pipedrive does not have native invoicing; Pipedrive Documents (Professional tier) handles proposal generation but not invoice tracking. For customers needing invoice history, we recommend importing as Notes with a standardized header format or setting up a FreshBooks or QuickBooks integration post-migration.

NinjaPipe Booking Pages (availability windows, contact associations) are exported as a written configuration document covering page settings and scheduling rules. Pipedrive's native scheduling tool or a Calendly integration replaces Booking Pages. We do not migrate scheduling logic as code; the configuration document is handed off for rebuild in the chosen tool.

Custom fields defined on NinjaPipe Contacts, Deals, and Pipeline Stages are enumerated during discovery and mapped to Pipedrive custom fields of equivalent type. Text fields map to text, numbers to number, dates to date, and dropdowns to drop-down custom fields. We create the destination custom fields in Pipedrive before any record import so that field assignments resolve on insert. Field labels are preserved; help text migrates as a note in the mapping document.

NinjaPipe Owners (sales reps assigned to Contacts, Deals, and Tasks) map to Pipedrive Users resolved by email match. Owners without a matching Pipedrive User go to a reconciliation queue for the customer's admin to provision the User account before record import resumes. Active vs. inactive status is preserved by setting the Pipedrive User's active flag accordingly.