Migrate from Berry crm to Salesforce Sales Cloud

Berry CRM Contacts map to either Salesforce Lead or Contact based on a lifecycle/status property we discover during the scoping export. If Berry CRM stores a status or type field that distinguishes qualified from unqualified contacts, we apply that as the split rule during migration. If no such field exists, all contacts migrate as Salesforce Leads for the customer's admin to convert post-migration. We preserve any email, phone, address, title, and custom field data from Berry CRM on the destination record.

Berry CRM Company records map directly to Salesforce Account. The company name becomes Account.Name and is used as the dedupe key during import. Any domain or website field in Berry CRM maps to Account.Website. We import Account before any Contact so that the AccountId Lookup relationship is satisfied at Contact insert time.

Berry CRM Deals map to Salesforce Opportunity. Deal name, amount, close date, and stage name transfer directly. We map the deal stage name to a Salesforce StageName value that matches or is configured in the destination org before migration. If Berry CRM stores a deal owner, we resolve that to the Salesforce OwnerId via the User mapping.

Berry CRM deal stage names become Salesforce StageName values in the Opportunity Sales Process. We configure the stage values in Salesforce before migration and map stage probability percentages to StageProbability. The customer chooses whether to use a single Sales Process or create separate Record Types per deal type during scoping.

Berry CRM Sales Quotes map to Salesforce Quote (available from Professional tier onward). Quote line items migrate to QuoteLineItem with PricebookEntry resolved at migration time. Quote status (draft, sent, accepted, rejected) maps to Salesforce QuoteStatus. Quote PDFs or attachments migrate as ContentDocument records linked to the Quote.

Berry CRM Product catalog entries (name, description, SKU, pricing) map to Salesforce Product2 records. We create Standard Price Book entries during the product import phase. Archived or inactive products in Berry CRM are flagged in the migration scope for the customer to decide whether to import or skip.

Berry CRM Price Books define price lists associated with products. We map them to Salesforce Pricebook2 records and create PricebookEntry records linking each Pricebook2 to the relevant Product2 with the specified unit price. The Standard Pricebook is set as default if no specific price book applies.

Berry CRM Projects have no direct Salesforce standard object equivalent. We migrate Projects to a custom Project__c object that we pre-create in the destination org during schema design, including fields for project name, status, start date, end date, associated company (Account lookup), and associated contact (Contact lookup). Project-to-task relationships become Task records with WhatId pointing to Project__c.

Berry CRM Tasks map to Salesforce Task with Subject, Status, Priority, ActivityDate, and Description preserved. Task assignment migrates by resolving any Berry CRM owner reference to Salesforce OwnerId via the User mapping. Tasks with a Contact association map WhoId to the migrated Contact record; tasks with a Deal association map WhatId to the migrated Opportunity.

Berry CRM Invoices (line items, totals, payment status, billing contact) have no direct Salesforce standard object equivalent. We migrate Invoices to a custom Invoice__c object pre-created during schema design, with fields for invoice number, date, total amount, status, and lookup relationships to Account and Contact. If the customer uses Opportunities for billing, we alternatively map Invoice data to the Opportunity record and its line items.

Berry CRM Owner references on Contact, Company, Deal, Quote, Project, Task, and Invoice migrate by resolving the owner email against the Salesforce User table in the destination org. Any Berry CRM owner without a matching Salesforce User enters a reconciliation queue for the customer's admin to provision the User before record import resumes.

Berry CRM allows custom fields on primary objects but the mechanism is not publicly documented. We detect all custom fields during the discovery export, capture their data types and values, then create explicit mapping rules and corresponding custom fields in Salesforce before any data import. Each custom field is logged in the mapping document with its source name, destination API name, and any transformation logic applied.