Migrate from Firmao CRM to Zoho CRM

Firmao Contact records map to Zoho CRM Contact. Standard fields (firstName, lastName, email, phone, address properties) transfer directly. The Firmao companyId reference resolves via companyName matching when we look up the destination Zoho Account record created from the same source Company. Tags stored as a comma-separated string on the Firmao Contact record migrate to Zoho's native Tag feature via the Tags API. If the source Firmao account is on Standard tier, customFields custom5, custom12 etc. will not be populated — we skip null-valued custom fields to avoid creating empty Zoho custom fields.

Firmao Company maps to Zoho CRM Account. The name field maps directly; industry, website, phone, and address properties map to their Zoho equivalents. Firmao stores no separate Account object type — Company is the only organizational record. We rename to Account during Zoho import so that Zoho's native Account-Contact relationship model is satisfied. Account is imported before Contact so that AccountId is available for Contact linking at insert time.

Firmao Deal maps to Zoho Deal. This object is gated on the source account's Professional tier — we confirm the active plan tier during scoping before attempting to extract Deal records. The deal stage names, value, owner, and companyId/dealId references transfer. We ask the customer to confirm their active Zoho Deal pipeline and stage names, then map Firmao stage values to the existing Zoho stage picklist. Closed-Lost and Closed-Won values from Firmao map to Zoho StageName transitions. Deal owner resolves via email match against the Zoho User list.

Firmao Task maps to Zoho Task. Subject, due date, status (pending/in progress/done), and priority transfer directly. The subClass/subId envelope on a Firmao Task stores its linked Contact or Deal reference — we extract the subClass type and subId value, resolve the subId to the destination Zoho Contact or Deal record by name match, and set the WhatId or WhoId accordingly. If the linked subClass record has not yet been migrated, the Task is held in a pending-relation queue until the parent object imports.

Firmao Product maps to Zoho Product. Product name, code, unit, and description transfer. The base price (standard price) maps to Zoho's List Price field. Firmao does not expose a separate Price Book object — if the customer uses customer-specific pricing in Firmao, those values are stored as customFields entries and we create Zoho Product custom fields to hold them. We extract the netPriceInStore and currentStoreState values per subClass=warehouse entry and map these to individual Zoho Inventory Adjustments or warehouse location records depending on the customer's Zoho Inventory configuration.

Firmao User records (name, email, role) map to Zoho CRM Users. We export the full user list from /svc/v1/user, then match by email against the Zoho destination org's existing User records. Any Firmao Owner referenced on a Deal or Task without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before the record import begins. Inactive Firmao users mapping to inactive Zoho users is acceptable for historical ownership preservation.

Firmao custom field keys (customFields.custom5, customFields.custom12, etc.) have no human-readable labels in the API response — the data import help file defines labels but requires login. We retrieve a sample record via GET first to enumerate which custom fields are populated, then request the customer's import documentation to cross-reference label-to-key mappings. Fields with no values in the sample export are flagged as potentially deleted and excluded. In Zoho, we pre-create the equivalent custom fields in the Fields API under the relevant module (Contacts, Accounts, Deals) using the label names from the customer's documentation before migration begins. Custom fields are available on Zoho Standard tier — no tier upgrade required.

Firmao Invoice maps to Zoho Invoice if the customer is migrating to Zoho Books or Zoho Invoice alongside CRM. The invoice header (number, date, due date, status, customer reference) transfers. Line items transfer as Zoho Invoice Line Items with product, quantity, rate, and tax code. If Zoho Books is not in scope, Invoice maps to Zoho CRM Quotes or Invoices module. Firmao's VAT invoice format and tax codes are preserved as text in the description field with a flag for the customer's admin to configure the Zoho tax structure post-migration.

Firmao Project is available on Professional and above. Project name, description, start date, and end date migrate to Zoho. Gantt and Kanban layout data (bar positions, column configurations) do not have API equivalents in Firmao and are not migrated. If the customer licenses Zoho Projects separately, Projects migrate to Zoho Projects with task associations carried over as Zoho Project tasks. If Zoho Projects is not in scope, we create a Custom Module in Zoho CRM to hold the project records and flag the layout for manual rebuild.

Firmao stores tags as a comma-separated string on the Contact or Company record. There is no dedicated /tags endpoint. We extract the tag string, split on comma, and create Zoho CRM Tag records via the Tags API, then associate them with the migrated Contact or Account. If the same tag name already exists in Zoho, we reuse the existing tag rather than duplicating.

Firmao pipeline stages are a property on the Deal object rather than a separate API entity. We export all Deals with their stage values and ask the customer to confirm the stage names and probability percentages they use. We map these to Zoho CRM Pipelines and Stage definitions via the Pipeline API, creating a Zoho Pipeline for each distinct pipeline used in Firmao. Stage probability percentages round to Zoho's allowed integer values.

Firmao Warehouse is not a top-level object — it appears as subClass=warehouse entries within the product modification log, returning netPriceInStore and currentStoreState per warehouse. We extract all subId variants per product during product export, then recreate each warehouse as a separate Zoho Inventory warehouse or location record, linking the product to each warehouse with the associated stock state and price. If the customer does not license Zoho Inventory, we store warehouse-level pricing in Product custom fields and note the stock state in the migration report for manual entry.