Migrate from Fireberry to monday CRM

Fireberry Contact records (name, email, phone, address, owner assignment, lifecycle stage) map 1:1 to Monday.com CRM People items in the People board. Monday.com's People board stores contact fields as native properties. We map contact owner assignment to a Person column on the item and preserve lifecycle stage as a Status or Dropdown column. The email address serves as the dedupe key during import.

Fireberry Company records (business name, industry, size, address, domain) map to Monday.com CRM Organization items in the Organizations board. Organization items are linked to Person items (Contacts) to preserve the company-contact relationship. The domain field maps to a Text column for web reference.

Fireberry Deal records (amount, stage, probability, expected close date, pipeline, linked Company and Contact) map to Items in Monday.com CRM's Deals board using the Deals CRM view. Deal amount maps to a Number column, probability to a Numbers column or Percentage column, expected close date to a Date column, and stage to the Status column that drives the Deals CRM view. We resolve the linked Company and Contact references by matching Organization and Person items already imported. Closed-Lost and Closed-Won outcomes are preserved as status values.

Fireberry pipelines with their stage order and probability percentages require reconstruction in Monday.com CRM because there is no native multi-pipeline object. Each Fireberry pipeline becomes its own board (or a separate group within a single Deals board) with a Status column whose values match the Fireberry stage names. Stage probability values are stored as a Percentage column on each deal item for reference. If Fireberry has multiple pipelines, we create multiple boards in Monday.com, one per pipeline, with consistent column schemas across boards.

Fireberry activity records (calls, emails, meetings, tasks with timestamps and owner IDs) map to Monday.com Item Updates, which are chronological entries on an item's feed. We preserve the activity type in the Update body and set the timestamp from the original Fireberry record. Monday.com does not have a typed activity object equivalent to HubSpot's engagements, so the type-label and duration information is preserved as text within each Update rather than as structured fields. Activity linking to the correct Contact or Organization item is resolved through owner email matching during import.

Fireberry user-defined Components that extend standard objects with custom fields map to Monday.com Custom Objects using the Dynamic mapping type, which allows a custom object to contain a set of subfields mapped onto an item. We enumerate every Fireberry custom object and its fields during schema discovery and create the equivalent Custom Object schema in Monday.com before import. Any multi-level lookup relationships in Fireberry custom objects are reviewed for manual mapping because Monday.com Custom Objects support flat subfield structures more naturally than deep hierarchies.

Fireberry automation rules are stored as trigger-action configuration that cannot be exported as reusable definitions and replayed at the destination. We capture each workflow's trigger type, conditions, and actions as a structured text record during migration scoping and deliver a written inventory of every active automation with its equivalent Monday.com automation builder syntax. The customer reviews the translated rules and rebuilds them manually in Monday.com's automation builder, which uses a When-If-Then-Do block structure. Fireberry automations that use URL-call triggers may require a third-party middleware review because Monday.com's native automation triggers operate within the board context.

Fireberry reporting views and dashboard configurations are not exportable as reusable definitions because the reporting schema is tied to Fireberry's internal object model. We migrate the underlying data (Contacts, Companies, Deals, Activities) so that Monday.com's dashboard widgets can be configured from scratch against the imported data. The customer rebuilds reports as board-level or dashboard-level widgets in Monday.com after migration. We do not include report migration in the standard scope.