Migrate from Firmao CRM to monday CRM

Firmao Contacts map to Monday.com People items within the CRM People board. Standard contact properties (name, email, phone, address, job title) map to typed Monday.com columns (text, email, phone, location, text). We extract tag values from Firmao's comma-separated tag property and map them to Monday.com Tags or a multi-select dropdown column depending on the board structure. Custom fields (customFields.customN) become individual columns in the People board — we create the column schema first, then import data second, because Monday.com requires column IDs before item creation via API.

Firmao Company records map to Monday.com Organization items in the CRM Organizations board. Company name becomes the Organization name. Industry, website, and address fields map to typed Organization columns. We create Organizations before People items so that the People-to-Organization link column resolves correctly on import. If the destination is configured as a single CRM board rather than separate People and Organizations boards, we map Companies to a dedicated Group within the board instead.

Firmao Deals map to Monday.com Deal items. This mapping is contingent on the customer's active Firmao plan: Deals are available on Professional and above. If the customer is on a Standard plan and has been using Deals in a limited capacity, we confirm during scoping whether Deals exist in the export and whether the customer intends to upgrade before migration or reconstruct Deal records manually in Monday.com. We map dealstage to a Monday.com Status column representing pipeline stages, dealValue to a Number column, and owner assignments to a Person column.

Firmao Tasks map to Monday.com items within a Tasks board or as items within a CRM board. We preserve assignee, due date, and status from Firmao. The subClass/subId relationship envelope that Firmao uses to attach a Task to a Contact or Deal is transformed into a Monday.com Connect board column linking the Task item to the relevant People or Deal item. Firmao's task modification history (subClass=task modification log entries) does not migrate as separate records; we import the current task state only.

Firmao Products map to items in a dedicated Monday.com Products board. Standard product fields (name, SKU, description) map to text columns. Base price migrates to a Number column. If the customer uses individual customer pricing (a Professional feature in Firmao), we map each price variant to a separate Number column or to a connected board relationship depending on the price model's complexity.

Firmao's warehouse stock is not a top-level object — it is embedded as subClass=warehouse entries in the product modification log, with netPriceInStore and currentStoreState as subId properties. Each warehouse variant per product is extracted as a distinct location record in Monday.com, creating a separate Location item for each warehouse. If the customer uses multi-location inventory tracking, we recommend a dedicated Inventory board with a Location column that groups items by warehouse.

Firmao Invoice records (VAT invoices, bills, receipts, accounting notes) do not migrate to Monday.com. Monday.com does not have a native accounting or invoicing module, and there is no standard invoice object in Monday.com Sales CRM. Invoice headers and line items cannot be meaningfully represented as board items without significant custom development. We flag all invoice records in the export and deliver a written record of the invoice count and field schema for the customer to evaluate dedicated accounting tools (Quaderno, Harvest, or similar integrations) post-migration.

Firmao Projects (Gantt and Kanban views, Professional and above) map to Monday.com boards. The project name, description, and date range migrate as board metadata. Individual project tasks map to items within the board. We do not migrate Gantt bar positions or Kanban column configuration; these are layout data with no semantic equivalent in Monday.com's board structure. We deliver a layout reconstruction guide describing the original Gantt and Kanban layout so the customer can rebuild the view in Monday.com's Timeline, Gantt, and Kanban views.

Firmao Users (name, email, role) are exported and used to resolve owner assignments on Deals, Tasks, and other records. The owner reference in each migrating record is resolved by matching the owner email to the corresponding Monday.com workspace member. If the Monday.com workspace does not yet have a member account for a given owner, we flag that record for manual User provisioning before import continues. We do not create Monday.com user accounts programmatically.

Firmao custom fields use dot-notation keys (customFields.custom5) with string values and no human-readable label in the API. We retrieve a sample record via GET first to enumerate which custom fields are populated, then cross-reference against the customer's import documentation. Only fields with populated values in the sample export are included in the migration. Each populated custom field becomes a new column in the target Monday.com board before item import. Empty custom fields are flagged and excluded. Column type (text, number, date, dropdown) is inferred from the value content.

Firmao stores files in a cloud storage vault (2GB on Standard, 10GB on Professional) but does not expose file blobs via the public REST API. Attachments cannot be extracted programmatically. We document the storage usage during scoping and advise the customer to download files manually from Firmao before account closure or to use the 14-day post-cancellation access window to retrieve critical documents.

Firmao does not expose email conversations, call logs, meeting records, or activity logs as discrete API objects. The platform surfaces email history through the CRM UI but there is no documented /activity or /email endpoint. We cannot migrate historical engagement data. We deliver a written record of the engagement objects present in the UI so the customer understands the scope of what is not being migrated before cutover.