Migrate from Berry crm to Microsoft Dynamics 365 Sales

Berry CRM Contact records map to Microsoft Dynamics 365 Contact. Standard fields (full name, email address, phone number, postal address) map to the Contact entity's name, emailaddress1, telephone1, and address fields. We use email address as the dedupe key during import. Contact-to-Company association from Berry CRM resolves to AccountId on the Contact record. Any custom fields detected on Contact during the discovery export are created as explicit fields on the Dynamics 365 Contact entity before migration and mapped by name and type.

Berry CRM Company records map to Microsoft Dynamics 365 Account. The company name maps to the Account name field, domain or website maps to the Website field, and address data maps to the address composite fields. We use company name as the dedupe key and resolve the Account record before importing any associated Contacts. Any company-specific custom fields from Berry CRM are created as explicit fields on the Account entity and mapped during the load phase.

Berry CRM Deals map to Dynamics 365 Opportunity. The deal name maps to the Opportunity name field, amount maps to estimatedvalue, close date maps to estimatedclosedate, and stage maps to a Sales Process stage value. We create a Sales Process in Dynamics 365 that reflects the Berry CRM pipeline stages before migration so that stage values are valid on insert. Deal-to-Contact and Deal-to-Company associations map to the Opportunity's contactid and customerid lookups respectively.

Berry CRM Sales Quotes map to Dynamics 365 Quote. Quote header fields (quote date, expiration date, status) map to quotedate, effiveDate, and statuscode. Line items from Berry CRM map to quotedetail records referencing the Quote and the associated Product2. Quote-to-Deal associations map via the Opportunity lookup on the Quote. We validate that the destination org has Quotes enabled (available from Professional tier) before planning this object in scope.

Berry CRM Products map to Dynamics 365 Product2. The product name maps to name, SKU maps to productnumber, and pricing data maps to standardcost or is used to create Price List Item entries in the default price book. We create Product2 records before Quote and Line Item migration so that product lookups are satisfied at insert time. Archived or inactive products from Berry CRM are migrated with a status flag for the customer to activate in Dynamics 365 post-migration if needed.

Berry CRM Projects are migrated as either Opportunities with a custom project-type Record Type (if the customer uses Microsoft Dynamics 365 Sales for project pipeline tracking) or as a custom Project entity created in Dataverse. We determine the target during scoping based on the customer's Dynamics 365 tier and intended use of the project data. Project status, associated contacts, and task breakdowns are mapped accordingly. If the customer licenses Project Operations, we can map to the Opportunity-based project model instead.

Berry CRM Task records map to Dynamics 365 Task. Task subject maps to subject, due date maps to scheduledend, assignee resolves to the OwnerId via User email matching, and completion status maps to statecode and statuscode. Task-to-Contact, Task-to-Company, and Task-to-Deal associations map to the Regarding (regardingobjectid) lookup on the Task record. Tasks are imported after Contacts, Companies, and Deals so that the lookup targets exist.

Berry CRM Invoices map to Dynamics 365 Invoice if the destination org has the Invoice entity enabled (Sales Enterprise and above). Invoice header fields (invoice number, date, total, payment status) map to invoicenumber, invoicedate, totalamount, and paymenttermscode. Line items map to invoicedetail records. Invoice-to-Contact and Invoice-to-Account associations map to the customerid lookup. We confirm Invoice module availability during scoping since it is not included in Sales Professional.

Berry CRM custom fields on any primary object (Contact, Company, Deal, Quote, Product, Project, Task, Invoice) are explicitly mapped during the discovery phase. We create matching custom fields in Dynamics 365 using the appropriate Dataverse field type (text, number, picklist, bit, datetime, currency) before migration begins. Custom field values migrate as part of their parent object import. Any picklist or multi-select custom fields in Berry CRM are mapped to Dynamics 365 OptionSet values created explicitly in the destination schema.