Migrate from Firmao CRM to HubSpot

Firmato contacts map directly to HubSpot contacts. The primary company link is resolved via email domain or the most-recently-modified company association and written as a HubSpot company association. If Firmato stores multiple companies per contact, all associations are preserved using HubSpot's associations API.

Firmato companies map directly to HubSpot companies. We translate the Firmato company name, domain, industry, employee count, annual revenue, phone, city, country, and website into their HubSpot equivalents. All HubSpot company properties are optional, so any Firmato fields absent from a record are skipped automatically without halting the import process, and we record the mapping in the field-mapping sheet for audit.

Firmato deals map to HubSpot deals but require two mapping steps: first, the deal must be attached to a HubSpot company via CompanyId — we resolve this from the deal's primary contact's primary company. Second, the Firmato deal stage name is mapped to the HubSpot deal pipeline stage. If Firmato uses multiple deal pipelines, we map each to a separate HubSpot pipeline with its own stage values.

Firmato tasks map to HubSpot engagements. Call tasks become HubSpot call engagements with the call disposition and duration preserved. Email activities map to HubSpot email engagements. Notes map to HubSpot notes attached to the contact record. All original timestamps and owner IDs are preserved on the engagement record.

Firmato users are resolved by email match against HubSpot owners. If a Firmato owner email does not match a HubSpot user, the record is assigned to a designated fallback HubSpot owner and the original owner ID is stored in a custom property for reconciliation. No record migrates without an owner assignment.

Every Firmato custom field is evaluated by type — text fields become HubSpot string properties, number fields become HubSpot number properties, and pick-list fields become HubSpot enumeration properties. We create the HubSpot property first, then import values. Any field that exceeds HubSpot's property name length limit is truncated and marked in the field-mapping sheet.

Firmato deal stage names are mapped one-to-one to HubSpot deal pipeline stages. Each HubSpot pipeline requires its own stage set, so multi-pipeline Firmato setups create multiple HubSpot pipelines. Stage order and probability from Firmato are applied to the HubSpot stage configuration during setup.

Firmato's project management and task modules have no HubSpot CRM equivalent. We export project and task records as CSV for reference but do not import them into HubSpot. Companies that need project tracking after migration use HubSpot's integrations with project tools or HubSpot's native tasks linked to deals.

Firmao’s invoicing module has no corresponding object in HubSpot CRM, so we export invoice and order records as CSV files for long‑term reference. The export captures all line‑item, payment, and status fields. If you require billing workflow after migration, you can activate HubSpot’s Quotes feature, connect a third‑party billing platform, or use HubSpot Payments, and the CSV data can be used to seed those systems.

Firmao’s product catalog and warehouse management are ERP functions outside HubSpot’s CRM scope. Product records are exported as CSV reference data. If the migration includes deal line items, we map Firmao product names to HubSpot line‑item product names, but the inventory and pricing logic stays in Firmao or a dedicated ERP.

For every migrated record we write the original Firmato internal ID into a HubSpot custom string property named Source_System_ID__c. This property persists on the contact, company, deal, and engagement objects, allowing the migration engine to identify source records for delta‑run imports, target rollback operations, and maintain a clear audit trail back to Firmato. The ID is set once and never overwritten during subsequent syncs.

At import HubSpot’s native Createdate and LastModifiedDate are set to the migration time, while the original Firmato creation and modification timestamps are stored in custom datetime properties called Original_Create_Date__c and Original_Modify_Date__c on each record. These custom fields preserve the true record history, allowing you to run historical reports and trend analysis using the original Firmato dates, and they remain read‑only after creation for audit consistency.