Migrate from Berry crm to monday CRM

Berry CRM Contact records map to Monday.com Items in a Contacts board or directly to Monday.com's native Contacts feature. Standard fields (name, email, phone, address) map to Monday.com's Name, Email, Phone, and Location column types. We extract what Berry CRM exposes in the export and map to typed Monday.com columns. Any custom fields on Contact in Berry CRM are flagged during discovery and created as additional column types in the destination board before import.

Berry CRM Company records map to Monday.com Organizations or Items in a Companies board. The company-contact relationship in Berry CRM maps to Monday.com's native person-to-organization link. Company-level custom fields migrate as additional columns in the destination board. If the customer uses Monday.com Organizations feature, we map Companies directly to Organizations; otherwise we use a board with a Contact link column.

Berry CRM Deals map to Monday.com Items within a CRM Deals board. Deal amount, close date, stage name, and associated contact all migrate as typed columns (Numbers, Date, Status, Connect boards or Person columns). Pipeline stages in Berry CRM map to Monday.com Status column values which we configure during board setup before migration. Deal-to-Contact associations are preserved through Monday.com's Connect boards column or Person column linkage.

Berry CRM Sales Quotes map to Items in a dedicated Quotes board. Quote line items, total amounts, status (Draft, Sent, Accepted, Rejected), and quote-to-deal association all migrate. We reconstruct quote line items as subitems or as a structured text column depending on the customer's Monday.com plan tier. Quote PDFs and attachments from Berry CRM migrate as file attachments on the corresponding Items.

Berry CRM Products map to Items in a Products board with columns for product name, description, unit price, and SKU. We extract the product catalog during discovery and pre-create the Products board in Monday.com before any Quote import begins so that the quote-to-product link resolves at migration time. Inactive or archived products are flagged for optional import.

Berry CRM Price Books define price lists associated with products. Monday.com does not have a native Price Book object, so we reconstruct price lists as additional Number columns on the Products board (one column per Price Book). This preserves the price list-to-product relationship while mapping to Monday.com's column-based data model. Customers with multiple Price Books receive a separate column for each list.

Berry CRM Projects contain tasks and metadata that do not map directly to Monday.com's CRM boards. We assess whether Projects represent work tracking (mapped to a Monday.com work management Board) or client-facing project records (mapped to Items in a CRM Projects board with subitems for tasks). The customer's intended use determines the board structure. Project metadata (status, dates, budget) maps to typed columns; tasks map as subitems or as Items in a linked board.

Berry CRM Task records (activity-level tasks tied to contacts, companies, or deals) map to Monday.com Subitems on the parent record or Items in a separate Tasks board. Task title, due date, assignee, and completion status map to Monday.com Text, Date, Person, and Status columns. If Tasks are tied to a specific Deal in Berry CRM, we link them via a Connect boards column in Monday.com to preserve the relationship. Standalone Tasks without a parent record are migrated as Items in a Tasks board.

Berry CRM Invoices map to Items in an Invoices board with columns for invoice number, date, line items, total, payment status, and linked contact. Invoice line items are reconstructed as subitems or structured text columns. Payment status (Paid, Unpaid, Overdue) maps to a Monday.com Status column. If Berry CRM generates invoice PDFs, we attach them to the corresponding Items. Invoice-to-contact association is preserved through the Person or Connect boards column.

Berry CRM custom fields are not publicly documented, which means we cannot pre-define mapping rules without a discovery export. During scoping we run a data extraction that identifies all non-standard fields on Contact, Company, Deal, Quote, and Invoice objects. Each discovered custom field is then created as a typed column in the corresponding Monday.com board before import. This discovery-heavy approach is required for Berry CRM specifically because the platform has no published schema reference.