Migrate from NinjaPipe to Freshsales

NinjaPipe Contacts map directly to Freshsales Contacts. Standard fields (name, email, phone, company, tags) map 1:1. Custom fields on Contacts are enumerated during discovery and mapped to Freshsales custom properties, preserving field types (date, number, dropdown, checkbox). Email address is the dedupe key during import. If the customer also uses the Sales module customer list, we deduplicate Sales customers against CRM Contacts by email before import, flagging duplicate email addresses for customer review.

NinjaPipe Pipelines (Kanban boards) map to Freshsales Pipelines. Stage names, stage order, and stage colours migrate as pipeline configuration. Each pipeline becomes a Freshsales Pipeline with stages configured as Status values. If the customer has multiple pipelines on NinjaPipe, each becomes a separate Freshsales Pipeline. Pipeline names and stage labels are preserved verbatim unless they exceed Freshsales character limits.

NinjaPipe Deals map to Freshsales Opportunities. Deal value maps to Amount, contact association maps to the Freshsales Contact lookup, owner maps to Freshsales User by email match, and the Pipeline Stage maps to Opportunity Stage. Deals without a Pipeline assignment receive a default pipeline in Freshsales. Custom fields on Deals migrate as custom properties on the Opportunity record.

NinjaPipe Orders live in the disconnected Sales module with no link to CRM Deals. We extract them as a separate export stream. If the customer is on Freshsales Suite with the native Orders module, we map Orders directly. If not, we create Notes linked to the associated Contact (resolved by email dedup from the Sales customer list) and attach a Task with order summary fields. We flag this decision at scoping because the mapping changes the Freshsales schema requirements.

NinjaPipe Products map to Freshsales Products with name, price, description, and SKU preserved. The Budget tracker in the Sales module has no direct Freshsales equivalent; we export budget values as a structured JSON attachment to the related Contact or Deal and note the gap in the migration report. Because NinjaPipe product import fails with a generic execution error, we batch products in groups of 10-20 during extraction and log which batches succeed or fail, retrying failed batches with sanitized values before final export.

NinjaPipe CRM Automations (trigger-action rules on Contacts, Deals, and Tasks) are exported as documented logic: trigger type, conditions, action sequence, and delays. We do not migrate Automations as live Freshsales Workflow rules because the trigger-action models differ structurally. The documentation maps each NinjaPipe trigger to a recommended Freshsales Workflow event (on-create, on-update, field-change, time-based) and is delivered as a written handoff for the customer's admin to rebuild in Freshsales Workflows.

NinjaPipe Form definitions and field structure migrate as Freshsales Forms with field types translated to Freshsales equivalents. Form submission history migrates as Contact records enriched with form attribution fields (form name, submission date) set as custom properties. Note that NinjaPipe's one-question-per-page form layout cannot be replicated in Freshsales Forms, which use a single-page layout; we document this layout difference in the handoff.

NinjaPipe Tasks (assigned to Contacts or Deals) migrate to Freshsales Tasks with title, description, due date, status, priority, and owner preserved. Owner resolution uses email matching against Freshsales Users. Completed versus open status is preserved. Tasks without a due date retain a null due_date in Freshsales. NinjaPipe's inability to sort the task list by due date has no bearing on Freshsales, which natively supports due-date sorting.

Custom fields defined on NinjaPipe Contacts and Deals are enumerated during discovery and mapped to Freshsales custom properties with type translation (date fields to Date, number fields to Number, dropdown fields to Picklist). Multi-select fields in NinjaPipe map to Freshsales Multi-select picklist. The Freshsales field builder is used to create all custom properties before the first record import runs, preventing import failures from missing field errors.

NinjaPipe Client Portal configurations (branding, logo, colour scheme, CNAME domain) cannot be exported as portable data. We preserve portal-accessible records (Contacts, Invoices, Documents) as standard CRM records, but the portal UI itself must be rebuilt in Freshsales by the customer's IT team. If the customer is on Freshsales Enterprise, the Freshsales Portal feature is the rebuild target; otherwise we note it as a post-migration admin task.