Migrate from Fireberry to Twenty CRM

Fireberry Contact records map to Twenty Person objects with name, email, phone, address, and lifecycle stage preserved. Fireberry's lifecycle stage (subscriber, lead, MQL, SQL, customer, evangelist) transfers to a custom field on Twenty Person since Twenty tracks person stage through a combination of Opportunities and CustomField picklists rather than a native lifecycle property. The mapping preserves email addresses as the dedupe key for Person import, and owner assignment transfers via email match against Twenty User records.

Fireberry Company records map directly to Twenty Company objects with domain, industry, size, and address preserved. The Company-to-Person relationship is maintained during migration by resolving the foreign-key link between the Fireberry Contact's company reference and the Twenty Company record, ensuring that each Person is linked to the correct Company at import time.

Fireberry Deal records map to Twenty Opportunity objects with amount, stage, probability, expected close date, and pipeline assignment preserved. Stage names and ordering transfer to Twenty Pipeline stages, and any custom Deal fields migrate as CustomFields on the Opportunity. We map deal owner via email resolution against Twenty Users before importing Opportunities.

Fireberry pipelines (including multi-pipeline setups) map to Twenty Pipeline definitions with their respective stage sequences. We extract the stage order, stage names, and stage probability percentages from Fireberry and configure matching Pipelines in Twenty before Opportunity import begins. Stages with no associated Deals are preserved as inactive stages in Twenty for audit completeness.

Fireberry custom objects defined through the Components system migrate to Twenty custom objects with equivalent API names. Twenty requires pre-creation of custom object schemas via its API before data import, so we enumerate every active Fireberry Component during discovery, create the corresponding Twenty custom object definitions, then import the records. Lookup relationships between custom objects and standard objects (Person, Company, Opportunity) are resolved via foreign-key mapping at migration time.

Fireberry custom fields on standard objects (Contacts, Companies, Deals) migrate to Twenty CustomField definitions attached to the equivalent standard object. We map Fireberry field types to Twenty types: text to Text, number to Number, date to Date, picklist to Select, multi-select to MultiSelect, checkbox to Boolean. Formula fields and computed fields do not migrate; their evaluated values are extracted as static data and mapped as read-only fields in Twenty.

Fireberry call activity records migrate to Twenty Task records with type=calls. Call duration, disposition, and recording URL transfer to custom fields on the Task. The linked Person or Company reference resolves via email and domain lookup to the corresponding Twenty record. Activity timestamps are preserved on the Task for timeline ordering.

Fireberry email engagement records migrate to Twenty Task records with type=emails. The email body, subject, sender, and recipient list transfer to the Task fields and linked Person records. Email attachments are noted as download references; Twenty's attachment handling is documented separately during scoping.

Fireberry meeting records migrate to Twenty Task records with type=meetings. Start time, duration, location, and attendee list transfer to the Task. Attendees resolve against the Twenty Person table via email match. Calendar integration context (Google Calendar, Outlook) is noted as a post-migration configuration item.

Fireberry note records migrate to Twenty Comment records linked to the corresponding Person, Company, or Opportunity. Note body transfers as the Comment text, with author and timestamp preserved. Rich-text formatting is converted to Twenty's supported markup. Notes attached to multiple records are duplicated as separate Comments on each linked entity.

Fireberry task records (as activity type, distinct from Deals) map to Twenty Task records with status, due date, priority, and assignee preserved. Assignee resolution follows the same email-match approach used for owner mapping on standard objects. Completed-at timestamps and task body transfer to Twenty Task fields.

Fireberry user records (name, email, role, team) map to Twenty User records. We resolve Fireberry owners by email against the Twenty User table during migration. Any Fireberry owner without a matching Twenty User is held in a reconciliation queue for the customer to provision the account before record import resumes. Inactive Fireberry users are flagged separately for the customer to decide whether to include their historical assignments.