Migrate from Onpipeline to monday CRM

Onpipeline Contacts migrate as Items in a Monday CRM board or dedicated Contacts board. Standard fields (name, email, phone, address) map to Name and corresponding text, email, phone, and address columns. Custom fields migrate as custom columns with type-mapped equivalents (date pickers, dropdowns, checkboxes). We preserve Tags as Labels on the Item and Lifecycle Stage as a single-select or text column. Email addresses serve as the dedupe key during import to prevent duplicate contact Items.

Onpipeline Companies migrate as Organizations in Monday CRM's Person and Organization model, either as Organization-linked Items in the CRM board or as Items in a separate Organizations board. The Company name maps to the Organization name field, and address, industry, and custom fields map to equivalent columns. Contact-to-Company linkage is preserved by setting the Organization column on each Contact Item to the migrated Company record.

Onpipeline Deals migrate as Items in a Monday CRM Deals board. Deal value maps to a Number column, stage maps to a Status column (group) reflecting the pipeline stage, and probability maps to a numeric column or percentage column. The Deal's linked Contact and optional Company are resolved to their Monday CRM equivalents (Person and Organization columns) at migration time. Custom fields on Deals migrate as custom columns on the Item. Closed-Lost and Closed-Won status are preserved as stage values in the Status column.

Each Onpipeline pipeline with its custom stage names and probabilities maps to a Status column in Monday CRM with one group per stage. We preserve the stage order and probability percentage as a separate column if the customer requires it for reporting. Multi-pipeline setups in Onpipeline map to multiple Status columns or multiple CRM boards depending on the customer's preferred structure in Monday.

Onpipeline Events (calendar appointments with datetime, duration, assigned user, and description) migrate as sub-items on the parent Deal or Contact Item in Monday CRM, with the sub-item Name capturing the event title and description fields mapped to text columns. We set the assignee to the mapped Monday User. Where sub-items are not used, Event content is preserved as an Update on the parent Item with a timestamp reference. Owner assignment is resolved by email match to the Monday User table.

Onpipeline Tasks migrate as sub-items on the parent Deal or Contact Item. Task title becomes the sub-item Name, due date maps to a Date column, status maps to a Status column, and priority maps to a Priority or Labels column. Completed status is preserved from Onpipeline's completed_at timestamp. Task assignment resolves the Onpipeline Owner to a Monday User by email.

Onpipeline Notes attached to Deals or Contacts migrate as Updates on the corresponding Monday CRM Item. The Note body is preserved as rich text in the Update, and the original Note timestamp is included in the Update attribution. We flag that Onpipeline Notes with file attachments require separate file migration as Item file attachments in Monday.

Onpipeline Products (name, SKU, price, stock quantity, custom fields) migrate as Items in a Monday Products board or as Items in a dedicated products area within the Deals board. SKU maps to a text column, price maps to a Number column, and stock quantity maps to a Numbers column if the customer requires it. We note that Monday CRM has no native inventory management, so stock quantity is informational unless a separate inventory integration is configured post-migration.

Onpipeline Quotes (line items, pricing, e-signature status, linked Contact and Deal) migrate as sub-items on the parent Deal Item in Monday CRM. Each sub-item captures the quoted product name, quantity, and price as columns. The Quote's total and e-signature status are stored as additional columns on the sub-item. We note that Monday CRM does not have a native Quote object, so Quote-level documents require a separate document attachment or integration with a quoting tool post-migration.

Onpipeline custom fields on Contacts, Companies, Deals, and Products migrate as custom columns in Monday CRM. We extract the full custom field schema during scoping, map field types to Monday column types (text, number, date, dropdown, checkbox, email, phone, link), and deploy the column configuration before record migration begins. Custom field values transfer as column values on each Item. Complex validation rules in Onpipeline do not migrate and are flagged for manual review in Monday.

Onpipeline Users assigned as Deal owners and activity assignees map to Monday Users by email match. We extract every distinct Onpipeline User referenced on Deals, Activities, and Notes and reconcile against the Monday workspace User list. Any Onpipeline User without a matching Monday User account is placed in a reconciliation queue for the customer's admin to provision before the migration resumes.

Onpipeline Tags applied across Contacts, Companies, and Deals migrate as Labels on the corresponding Monday CRM Items. Multi-tag assignments per record are preserved as multiple Label values. We note that Monday Labels are board-scoped, so if the customer uses Tags across different object types that will live in separate boards, the Label set may need to be recreated per board.

Onpipeline Invoices (header, line items, payment status, linked Deal) have no native Monday CRM equivalent. We migrate Invoice header metadata and line item data as columns on a sub-item or as a document attachment on the Deal Item, with payment status stored as a Status column. The customer should plan to either use Monday's native invoice workaround or connect a third-party invoicing tool (Stripe, QuickBooks Online, Zoho Invoice) post-migration. Recurring invoice automation from Onpipeline Advanced plan is flagged as a configuration that must be rebuilt in the customer's chosen invoice integration.