Migrate from Berry crm to HighLevel

Berry CRM Contact records map to GoHighLevel Contact with name, email, phone, and address fields preserved. The primary challenge is that Berry CRM's exact field schema is not publicly documented, so we detect all available fields during discovery export and create explicit field-mapping rules for each one before import. GoHighLevel Contact custom fields are created via Settings > Custom Fields with object scoping before the migration pipeline runs.

Berry CRM Company records map to GoHighLevel Company (or Location within a Company). We preserve the contact-to-company relationship by resolving the company reference on each Contact during import. Any company-specific custom fields from Berry CRM are mapped to GoHighLevel Company custom fields or Location-level custom fields depending on the customer's data model preference established during scoping.

Berry CRM Deals map to GoHighLevel Opportunities with stage name, amount, close date, and associated contact/company preserved. Pipeline stages from Berry CRM become GoHighLevel pipeline stages, which we configure as part of the schema setup phase. Stage probabilities and stage ordering are mapped explicitly since Berry CRM and GoHighLevel stage naming conventions differ.

Berry CRM Quotes contain line items, pricing, and status tied to a Deal or Contact. We map Quote headers to GoHighLevel Opportunity records with the quote amount and status preserved. Quote line items are stored in a GoHighLevel Custom Table linked to the Opportunity, since GoHighLevel does not have a native Quote object equivalent to Salesforce's Quote. We flag quote PDF attachments for manual upload post-migration.

Berry CRM Products map to GoHighLevel Products in the Product Catalog. Product name, description, and pricing migrate. If Berry CRM stores multiple price points per product (via Price Books), we map these to GoHighLevel Custom Tables or product variant fields depending on the destination's pricing model structure. Archived or inactive products are flagged for the customer's admin to review before import.

Berry CRM Price Books define named price lists associated with Products. Since GoHighLevel does not have a native Price Book object, we map Price Book data to a Custom Table linked to the Product Catalog, preserving the named price list structure. The customer chooses a Custom Table name during scoping that matches their business terminology.

Berry CRM Projects contain project metadata, status, and associated tasks. We map project-level metadata to a GoHighLevel Custom Table with status and dates preserved. The project's child tasks migrate to GoHighLevel Tasks linked to the relevant Contact or Opportunity record, preserving due dates and assignees. The depth of project-task data migration depends on the export completeness from Berry CRM.

Berry CRM Tasks migrate to GoHighLevel Tasks with title, due date, assignee (resolved via email to GoHighLevel User), and completion status. Task associations to Contacts, Companies, or Deals are preserved via GoHighLevel's task linking fields. Completed tasks are imported with their completion status; open tasks import as open.

Berry CRM Invoices contain line items, totals, payment status, and contact associations. We map invoice headers to a GoHighLevel Custom Table with status and totals preserved. Invoice line items are stored as a related Custom Table with the invoice header as the parent. Payment status and invoice-to-contact links are preserved in custom fields.

Berry CRM custom fields on any primary object (Contact, Company, Deal) are detected during discovery export and mapped to GoHighLevel Custom Fields created via Settings > Custom Fields. GoHighLevel requires custom fields to be created before import with the correct field type (text, number, date, dropdown, checkbox). We map Berry CRM field types to GoHighLevel equivalents during the discovery phase and create all destination custom fields before any data moves.