Migrate from NinjaPipe to Twenty CRM

NinjaPipe Contacts map directly to Twenty Persons. Standard fields — name, email, phone, company, tags — map to their Twenty equivalents. Custom fields defined on Contacts in NinjaPipe are enumerated during discovery and recreated as custom fields in Twenty via Settings → Data Model before import. The original NinjaPipe contact ID is preserved in a custom field ninjapipe_id__c for cross-reference during reconciliation.

NinjaPipe Contacts with an associated company name map to Twenty Companies. Where a NinjaPipe Contact has a linked Company record rather than just a text company name, we resolve the relationship and link the Person to the Company via the Twenty Person.organizationId field. If multiple NinjaPipe contacts share a company name without a formal Company record, we optionally deduplicate them into a single Twenty Company at the customer's direction.

NinjaPipe Deals map to Twenty Opportunities with deal value preserved as amount, stage assignment mapped to Twenty Opportunity stage values, and the owning contact linked via the Opportunity.personId field. The original pipeline name from NinjaPipe becomes the Opportunity name in Twenty unless a title field is present. Deals without a Pipeline assignment are imported as Opportunities with a default stage defined during scoping.

NinjaPipe Pipelines (Kanban boards) map to Twenty Opportunity stage configurations. Each pipeline stage name in NinjaPipe becomes a Twenty stage value in the Opportunity stage picklist. Stage order and colour values are preserved as stage metadata. If NinjaPipe has multiple pipelines, we create multiple stage value sets or a custom picklist field pipeline_name__c to distinguish them in Twenty, depending on the customer's reporting structure.

NinjaPipe Tasks map directly to Twenty Tasks. Due dates, task titles, descriptions, assignees, and open/closed status transfer 1:1. We flag that NinjaPipe's task list cannot currently be sorted by due date — this limitation does not carry over; Twenty's task list supports due-date sorting natively. Task assignees resolve by email against the Twenty User table during import.

NinjaPipe Products live in the disconnected Sales module with no link to Deals. We export the product catalog (name, price, description, SKU) as a custom object in Twenty called Product. If the customer uses NinjaPipe Orders to track line items on Deals, we import order line items as Opportunity Line Item records linked to Opportunities, with the product resolved via the Product custom object. The mapping decision is confirmed during scoping based on reporting requirements.

NinjaPipe Orders are manually entered in the Sales section with no link to Deals, Quotes, or Invoices in the CRM. We export Orders as standalone records and present two options: merge them into existing Opportunities as line items (if a NinjaPipe Deal can be associated by customer or date logic), or create a custom Order object in Twenty for post-migration reporting. The customer chooses during scoping; we do not auto-merge without confirmation because the merge logic is heuristic.

NinjaPipe Invoices carry line items, totals, status, and contact association. We export Invoice metadata as a custom object in Twenty called Invoice. Financial ledger entries do not migrate. If the customer uses NinjaPipe Invoices primarily for client-facing document delivery rather than accounting, we alternatively attach invoice PDFs as Notes on the related Twenty Person or Opportunity.

NinjaPipe Automation Workflows (trigger-action rules on Contacts, Deals, Tasks) are exported as a written inventory: trigger type, conditions, action sequence, and affected objects. We do not migrate workflows as executable code into Twenty because the automation models differ structurally. The inventory document maps each NinjaPipe workflow to a Twenty workflow builder equivalent and is handed off to the customer's admin for rebuild post-migration.

NinjaPipe Form definitions (field structure, routing logic, submission-to-contact mapping) are exported as a JSON schema and a written form inventory. Because Twenty CRM has no native form builder, we recommend integrating an external form tool (Tally, Typeform, or Google Forms) via webhook to the Twenty REST API, creating a Person record on submission. Form submission history migrates as Person records enriched with the form field values.

NinjaPipe Booking Pages (appointment scheduling linked to Contacts) are exported as calendar availability settings and booking-to-contact associations. Twenty CRM has no native scheduling feature; we recommend connecting a third-party calendar tool (Cal.com, Calendly) via webhook to create a Task or Note on the relevant Person record. Availability windows are documented for manual configuration in the chosen scheduling tool.

NinjaPipe custom fields defined on Contacts and Deals are enumerated during discovery and mapped to Twenty custom fields created via Settings → Data Model before any data import. Field type translation is applied: NinjaPipe date fields map to Twenty date fields, number fields to number fields, dropdown fields to Twenty select fields. Multi-select and checkbox fields receive special attention because Twenty has reported 'Migration execution failed' errors when updating multi-select fields via API — we apply these in small batches with error retry logic.