Migrate your Firmao CRM data

Contacts are a first-class object accessible via GET and POST at the /svc/v1/contact endpoint. Custom contact fields follow the customFields.customN naming convention. We map all standard contact properties 1:1 and preserve the link to the parent Company by matching on companyName or a provided external ID.

Companies are exported and imported via the /svc/v1/company endpoint. Where the destination uses Accounts or Organizations, we rename the object at import time. No known schema instability in the standard company fields.

Deals are available on Professional and above tiers. The object supports pipeline stage, value, and owner assignment. Stage names vary by organization — we ask customers to confirm their active stages before mapping so we do not import deprecated or deleted pipeline stages into the new system.

Tasks are accessible via /svc/v1/task and include assignee, due date, and status. We preserve the contact or deal association using the subClass/subId envelope that Firmao uses for object relationships. Completed vs. open status is mapped to the destination's equivalent lifecycle field.

Products are managed at /svc/v1/product with per-warehouse stock state tracked via the subClass=warehouse property. We export the netPriceInStore and currentStoreState fields per warehouse and recreate the warehouse structure in the destination if supported.

Projects support Gantt and Kanban views on Professional and above. We migrate the project name, description, dates, and task associations. Visual layout data (Gantt bar positions, Kanban column configuration) does not export and must be rebuilt in the destination.

Firmao generates VAT invoices, bills, receipts, and accounting notes. Invoice records include line items, tax codes, and payment status. We map invoice headers and line items to the destination's equivalent invoice or bill object, preserving total amount and currency.

Warehouse is a subClass of the product object rather than a top-level entity. We extract stock levels and pricing per warehouse during product export and recreate the warehouse list in the destination, then reassociate product quantities.

Users are accessed via /svc/v1/user and include name, email, and role. We export the user list and map owner assignments on Deals and Tasks. User-to-contact ownership links are preserved; the destination must have corresponding user records or we assign to a default owner.

Custom fields are defined in Professional and above under the object's Settings section. They are referenced in the API using dot-notation keys like customFields.custom5, and values are strings. We export all custom field values as strings and map them to the destination's corresponding custom property, flagging type mismatches (date vs. text, multi-select vs. single-select) for review.

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 in this tier. We recommend exporting the file inventory as a metadata list for manual re-upload.

Email conversations and activity logs are not exposed 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 email threads automatically.

Tags are referenced on contacts and companies but there is no dedicated /tags endpoint. We extract tags as a comma-separated property on the contact or company record and map them to the destination's tag or label field, splitting on comma to populate the target's multi-value tag format.

Pipeline stages are defined per organization and are not a separate API object — they are a property on the Deal object. We export the deal records including the current stage value, then ask the customer to confirm the destination pipeline stage names before import to avoid orphaning deals in non-existent stages.