Migrate from Berry crm to Twenty CRM

Berry CRM Contact records map to Twenty Person. We extract name fields, email, phone, and address and write them to Twenty's Person object fields. Berry CRM contact-company associations preserve as Person.companyId lookup. Any custom fields on Berry CRM contacts require pre-creation in Twenty via Settings -> Data Model before import because Twenty's Person standard fields are intentionally sparse and new installations start without fields like jobTitle or department pre-built.

Berry CRM Company records map directly to Twenty Company. The company domain becomes the Website field if present. Company is created before Person import so that the Person.companyId lookup relationship resolves on insert. Any custom fields on Company (industry, employee count, type) are pre-created in Twenty's metadata schema as custom fields on the Company object.

Berry CRM Deals map to Twenty Opportunity. The dealstage value maps to Twenty Opportunity.stageName values, which we configure as picklist options during workspace setup. Closed-won and closed-lost status and amounts migrate as Opportunity.amount and Opportunity.stageName. Deal-close date maps to Opportunity.closeDate. If Berry CRM has multiple pipelines, we create multiple Opportunity record types in Twenty during schema setup.

Berry CRM Sales Quotes do not have a native equivalent in Twenty's standard object set. We map quotes to a custom Quote object created via Twenty's /metadata API, with fields for quote number, total amount, status, linked contact or company, and line items as a JSON or linked custom object depending on the quote's complexity. If quotes are simple, we optionally store them as Note records on the linked Opportunity.

Berry CRM Product catalog entries (name, description, pricing) map to a Twenty custom Product object created via the metadata API. Product pricing migrates as a custom price field. We flag inactive or archived products for optional exclusion during scoping.

Berry CRM Price Books define named price lists associated with products. We map Price Books to a Twenty custom PriceList object, with the Product-to-PriceList relationship preserved as a lookup field on the custom Product object. If the customer's price book structure is simple, we fold pricing into the Product object directly and skip the separate object.

Berry CRM Project records migrate to a Twenty custom Project object created via the /metadata API. Project metadata (name, status, start date, end date) maps to custom fields on the Project object. We also create a custom Tasks sub-object linked to Project if the project has significant task structure, so that project-task hierarchy is preserved rather than flattened.

Berry CRM Task records map directly to Twenty Task. We extract task title, due date, completion status, assignee (resolved via email to Twenty workspace member), and the linked contact, company, or deal as the Task's热血_id. Tasks with no parent record link migrate as standalone tasks. Completion status maps to Task.status.

Berry CRM Invoice records (line items, totals, payment status, contact association) map to a Twenty custom Invoice object created via the metadata API. Invoice-to-contact or invoice-to-company relationships migrate as lookups to the Person or Company records already created. Payment status becomes a select field with options matching the original values. Historical invoices are often candidates for exclusion if they predate two years, pending scoping discussion.

Berry CRM allows custom fields on primary objects, but the mechanism is not publicly documented. During discovery export, we detect every custom field name, type, and value set and create matching custom fields in Twenty via Settings -> Data Model before data import. Field type mapping is conservative: unknown text-like fields map to Twenty text fields, and numeric fields map to number fields. We validate the custom field creation in a staging pass before the full import runs.

Berry CRM owners map to Twenty workspace members by email address. We extract every distinct owner referenced on contacts, companies, deals, and tasks and match against Twenty User.email. Owners without a matching workspace member go to a reconciliation queue for the customer's admin to provision before record import continues.