Migrate from Pipeliner CRM to monday CRM

Pipeliner Account records map to Company Items on a Monday.com CRM People Board. The Account Name maps to the Company Name text field, and Account Address fields map to Monday.com Location or text columns. We deduplicate by Company Name during import. If the destination uses separate People and Companies Boards, Accounts land on Companies and Contacts land on People with a Connect Boards column linking the Contact Item to its parent Company Item.

Pipeliner Contact records map to People Items on a Monday.com CRM People Board. Name, Email, Phone, Job Title, and custom Contact fields map to equivalent Monday.com column types (Text, Email, Phone, Text). Each Contact Item receives a Connect Boards column pointing to its parent Company Item resolved via the Pipeliner Account-CONTACT relationship extracted at migration time.

Pipeliner Lead records map to Items on a dedicated Monday.com Leads Board. We create this Board during schema setup if the customer's Pipeliner instance contains active Leads. Lead Status maps to a Status column; lead score maps to a Numbers column; lead source maps to a dropdown or text column. Unconverted Pipeliner Leads land as-is; converted Leads that already have Account and Contact associations are migrated as Contact records with the lead conversion flag preserved as a custom column.

Pipeliner Opportunity records map to Deal Items on Monday.com CRM's Deals Board. Deal Name maps to Item Name, Deal Value maps to the Numbers column or Deal Value column (depending on Monday.com CRM plan), and Close Date maps to a Date column. The Opportunity-Account relationship becomes a Connect Boards column linking the Deal Item to the corresponding Company Item. The Opportunity-Contact relationship (Pipeliner allows multiple Contacts per Opportunity) maps to a Contact Connect Boards column or multiple Connect Boards column entries resolved from the Pipeliner Opportunity-CONTACT junction records extracted during migration.

Pipeliner pipeline stages map to Monday.com Status column options on the Deals Board. We collapse per-user stage overrides (a Pipeliner gotcha where the same Opportunity displays different stages to different users) to the primary admin-defined pipeline schema before mapping. Each Pipeliner stage name becomes a Status option; stage probability percentages from Pipeliner are stored as Numbers columns on the Deal Item for reporting. If multiple Pipeliner pipelines exist, they map to separate Deals Boards or separate Groups within a single Deals Board, at customer preference.

Pipeliner Quotes linked to Opportunities map to Monday.com Subitems on the corresponding Deal Item, or to Document columns if the customer uses Monday.com's quoting module (included in Pro+). Quote line items become Subitem rows with item name, quantity, and price columns. Product associations from Pipeliner's Product Grid are resolved during migration by matching Product names or SKUs to Monday.com product catalog entries.

Pipeliner Tasks and Appointments linked to Accounts, Contacts, or Opportunities migrate as Updates, Subitems, or a dedicated Activity Board depending on the customer's Monday.com plan and preference. Call disposition, duration, and meeting location map to text or numbers columns. We preserve the Activity parent reference by linking the Activity Item to the corresponding Contact or Deal Item via Connect Boards column. Calendar-specific fields (recurrence rules, attendee status) cannot be fully represented in Monday.com and are flagged for manual verification.

Pipeliner custom entity types (beyond the eight standard objects) map to Monday.com Boards with columns configured to match the source entity's field schema. We extract the custom entity field definitions during discovery, map each field to the nearest Monday.com column type (Text, Number, Date, Dropdown, Connect Boards, etc.), and create the destination Board structure before importing any data. Custom entities that reference standard entities (Accounts, Contacts, Opportunities) use Connect Boards columns for the relationship. This mapping requires per-migration custom scoping because Pipeliner's custom entity support is fully open-ended.