Migrate from Firmao CRM to Salesforce Sales Cloud

Firmao Contacts map to Salesforce Lead if the contact has no associated Deal and the customer intends to qualify them as prospects first. Contacts with an active dealId or a high custom field score map to Salesforce Contact attached to an Account. We extract Firmao contact.companyId to resolve the parent Account before Contact import, and preserve any Firmao tags as a multi-select picklist field on the Salesforce record.

Firmao Company records map directly to Salesforce Account. The companyName becomes the Account Name; address fields map to BillingAddress. Account is imported before any Contact so that the AccountId lookup is satisfied at Contact insert time. We use companyName as the dedupe key during import to prevent duplicate Account creation.

Firmao Deals map to Salesforce Opportunity. We verify during scoping that the customer's Firmao account is on Professional or above — Deals imported into a Standard-plan Salesforce org will land but the Opportunity pipeline UI will not display them. The Firmao dealstage property maps to the Salesforce StageName tied to a pre-configured Sales Process. Deal owner maps via email match to the Salesforce User ownerId.

Firmao pipeline stages are a property on the Deal object, not a standalone API entity. We export all Deal records to collect the distinct stage values, then create matching Opportunity Stages in Salesforce with corresponding probability percentages. Each stage gets a StageProbability value approximating the original Firmao distribution.

Firmao Tasks map to Salesforce Task with Status, Priority, and ActivityDate preserved. Firmao's subClass/subId envelope stores the task's relationship (contactId, dealId) — we resolve the subId against the imported Account, Contact, or Opportunity to set the WhatId or WhoId on the Salesforce Task. Task assignment migrates by matching the Firmao userId to the Salesforce User record by email.

Firmao Products map to Salesforce Product2 records. We extract the base product fields (name, sku, unit, description) and also pull all subClass=warehouse entries nested in the GET /product response, including netPriceInStore and currentStoreState per warehouse location.

Firmao Warehouse is not a top-level object — it appears as subClass=warehouse entries inside the product response, each with a distinct subId. We extract every warehouse variant per product and create individual Inventory Location records (or custom Location__c records if Inventory Management is not enabled) linked to the corresponding Product2. The netPriceInStore and currentStoreState values migrate as custom fields on the Location record.

Firmao Users map to Salesforce Users by email match. We export the complete user list including role and active status, then match each owner reference on Contact, Company, Deal, and Task to the corresponding Salesforce User record. Any Firmao User without a Salesforce match enters a reconciliation queue for the customer's admin to provision before record import begins.

Firmao custom field keys (customFields.custom5, customFields.custom12) have no self-documenting labels in the API response. We retrieve a sample record via GET first, enumerate all non-null custom field keys, cross-reference against the customer's import documentation, and exclude any fields that are null across the sample (indicating a deleted field). We pre-create matching custom fields in Salesforce with the appropriate field type before migration, using the customer's provided labels for readability.

Firmao Invoices (VAT invoices, bills, receipts, accounting notes) are ERP-level records that have no direct Salesforce standard equivalent. Sales Cloud does not include a native invoicing module at the Professional tier. We flag Invoice as out-of-scope for standard migration and recommend the customer evaluate Salesforce Invoicing (limited availability) or an AppExchange CPQ plus billing app (Conga, BillingPlatform). We export the invoice headers and line items as a CSV deliverable for the customer's billing team to review.

Firmao Projects are available on Professional and above and include name, description, dates, and task associations. Visual layout data (Gantt bar positions, Kanban column configuration) does not migrate — these are rendering properties, not data. We migrate the project name, description, start and end dates, and the linked task associations as a Project__c custom object in Salesforce with a related Task list.

Firmao tags appear as comma-separated values on the Contact or Company record. There is no dedicated /tags endpoint. We extract the tag string, split on comma, and map to a Salesforce multi-select picklist field on the appropriate record. If the customer uses tags for content or campaign classification, we map them to Salesforce Topics with TopicAssignment records based on the customer's preference.