Migrate from NinjaPipe to Nutshell

NinjaPipe Contacts map directly to Nutshell People. Standard fields (name, email, phone, company, tags) translate 1:1 to Nutshell's Person object fields. Custom fields on NinjaPipe Contacts are enumerated during discovery and mapped to Nutshell Person custom fields (text, long text, currency, date, dropdown, or checkbox). Contact owner assignment maps to Nutshell owner_id via email match. Tags from NinjaPipe migrate to Nutshell's tag field or to a multi-select custom field depending on the customer's tagging usage pattern.

NinjaPipe Company records map to Nutshell Company. The company name, domain, address, phone, and industry fields translate directly. Nutshell Companies and People are linked via the person-company association field. If the source data has contacts without a company association, we preserve the relationship as a Company record created alongside the Person with a manual association flag for the admin to confirm post-import.

NinjaPipe Pipelines map to Nutshell Pipelines, available on Pro tier ($42/user/mo) and above. Each NinjaPipe pipeline becomes a Nutshell Pipeline with stage names, stage order, and stage colors preserved. On Nutshell Starter or Growth tiers (no native pipeline UI), we migrate pipeline stages as a custom Opportunity field (pipeline_stage__c) with dropdown values. The customer selects the target tier during scoping.

NinjaPipe Deals map to Nutshell Opportunities. Deal value maps to Opportunity amount, contact association maps to the Opportunity's linked Person, and pipeline stage maps to the Nutshell Pipeline stage. If Nutshell Starter or Growth is selected, stage assignment is stored in a custom field rather than a native pipeline. Closed-Lost and Closed-Won deal statuses translate directly to Nutshell Opportunity lost and won states.

NinjaPipe Automation Workflows scoped to Contacts, Deals, and Tasks are exported as written rule logic (trigger type, conditions, action sequence). They do not migrate as executable code to Nutshell because NinjaPipe's trigger-action model and Nutshell's automation model (Pro tier email sequences, scheduled tasks) are structurally different. We deliver a written inventory of every active Workflow with its configuration and a recommended Nutshell equivalent for the customer's admin to rebuild.

NinjaPipe Invoice records (line items, totals, status, contact association) map to Nutshell Invoice if the destination is Pro tier or above. Invoice PDF attachments migrate as file records. Nutshell Starter and Growth tiers do not include native invoicing, so invoices migrate as completed Opportunity records with invoice data stored in a custom field block for reference. We flag the tier requirement during scoping.

NinjaPipe Products from the Sales module catalog (name, price, description, SKU) map to Nutshell Product records. NinjaPipe's product catalog lives in the disconnected Sales module — there is no foreign key linking it to CRM Deals. We export Products as standalone records and advise whether they should be associated with Nutshell Opportunities via Price Book entries post-import. The generic execution failure error that affects product import in NinjaPipe does not block outbound migration.

NinjaPipe Orders in the Sales module have no linkage to CRM Deals or Contacts — they are manually entered standalone records. We export Orders as a separate data stream and offer two strategies: migrate Orders as standalone Opportunity records (one per Order) with a custom order_number__c field, or merge them into existing CRM Deals if the customer can provide a mapping. The N:1 merge path requires customer-supplied mapping and adds scoping time.

NinjaPipe Tasks assigned to Contacts or Deals map directly to Nutshell Tasks. Due dates, task titles, descriptions, owners, and completed vs. open status migrate directly. NinjaPipe's task due-date sorting limitation does not affect the data migration; we export all tasks with their original due dates and completion timestamps intact.

NinjaPipe Form definitions and field structure are exported as a written form inventory. Submission history migrates as Person records enriched with form-specific field values stored in custom Person fields. The form UI itself cannot be migrated because NinjaPipe's form builder enforces single-question-per-page layout that cannot be replicated in Nutshell's intake model. We document the form fields requiring rebuild in Nutshell.