Migrate from Berry crm to Freshsales

Berry CRM Contact records map to Freshsales Contact. Standard fields (name, email, phone, address) transfer directly. We run a discovery export to capture the exact field names and types present in the Berry CRM instance before building the field map, since the schema is not publicly documented. Freshsales uses first_name and last_name as separate fields; we split full-name contacts accordingly. Any custom fields on Contact are detected during discovery and mapped to Freshsales custom fields created in Admin settings before import.

Berry CRM Company records map to Freshsales Account. Company name maps to display_name, domain or website maps to Freshsales website field. The Company-to-Contact relationship is preserved by inserting Accounts before Contacts and resolving the account_id lookup on each Contact record at import time. Company-specific custom fields detected during discovery map to Freshsales Account custom fields.

Berry CRM Deals map to Freshsales Deals. Stage name, amount, close date, and owner transfer directly. We map the Berry CRM pipeline stages to Freshsales deal stages, which are configurable per deal pipeline in Freshsales Admin settings. If Berry CRM uses multiple pipelines, we create corresponding Freshsales deal pipelines and map stage values per pipeline. Owner resolution uses email matching against Freshsales Users.

Berry CRM Sales Quotes map to Freshsales Deal Quotes if the destination plan includes the Quotes module (Growth and above). Quote line items map to Quote Items with product reference, quantity, and pricing. If the destination plan does not include Quotes, we map quote metadata (amount, status, date) to custom fields on the linked Deal and flag the quote line items as a separate import task with the customer's admin to configure in Freshsales.

Berry CRM Products map to Freshsales Products. Product name, description, and SKU transfer directly. Pricing information from Berry CRM Price Books maps to Freshsales standard price entries on the Product record. If a product has multiple price points from different Price Books, we create one Product record with multiple price entries or flag for the admin to consolidate during scoping.

Berry CRM Price Books define named price lists associated with products. Freshsales does not have a separate Price Book object; instead, it uses standard price book entries on each Product. We map the Price Book-to-Product relationship by creating Product records first, then adding standard price entries from each Berry Price Book. If multiple Price Books contain different prices for the same product, we flag this during scoping as a pricing conflict requiring admin decision.

Berry CRM Projects have no direct Freshsales equivalent. Freshsales does not include a native project object. We offer two migration strategies: (1) Map Project metadata to a Freshsales Deal with custom project fields, or (2) Map Project to a Task group using parent-child Task relationships. The customer chooses the strategy during scoping. Project status, description, and associated milestone dates transfer as custom fields or task metadata depending on the chosen strategy.

Berry CRM Tasks map to Freshsales Tasks. Task title, due date, assignee, and completion status transfer directly. If a Task is associated with a Contact, Company, or Deal in Berry CRM, we resolve the corresponding Freshsales record ID and set the task's link (contact_id, account_id, or deal_id) at import time. Owner resolution uses email matching.

Berry CRM Invoices map to Freshsales Invoices if the destination plan includes the Invoice module (Growth and above). Invoice line items, totals, payment status, and invoice-to-contact associations transfer directly. If the destination plan does not include Invoices, we map invoice metadata to custom fields on the linked Contact or Deal and flag the line items for manual recreation or a separate invoice-specific migration scope.

Berry CRM allows custom fields on primary objects but the mechanism is not publicly documented. We detect all custom fields during the discovery export phase, identify their types (text, number, date, picklist, checkbox), and create matching Freshsales custom fields in Admin settings before importing any records. The custom field mapping is explicit per field, per object, with the customer's admin confirming field type and label alignment before the import pipeline runs.