Migrate from Firmao CRM to Microsoft Dynamics 365 Sales

Firmao Contacts map to either Dynamics 365 Lead or Contact. We apply a split rule based on the customer's lifecycle definition in Firmao: contacts with an assigned owner and active deal association map to Contact attached to an Account; contacts without deal associations and with an unqualified status map to Lead. We preserve Firmao's custom field values (customFields.customN) in custom Dataverse attributes typed to match (string, number, date, or picklist). The WhoId on any related Activity records is resolved after the split.

Firmao Companies map directly to Dynamics 365 Accounts. The company domain or website field from Firmao becomes the Account Website attribute and serves as the deduplication key during import. Firmao does not expose internal IDs in GET responses, so we use companyName as the matching anchor. Account must be created before any Contact import so the AccountId lookup is satisfied at Contact insert time. Multi-address companies from Firmao map to the primary address fields on Account with additional addresses preserved in custom address fields.

Firmao Deals map to Dynamics 365 Opportunities. This object is gated behind Firmao Professional tier — we confirm the active plan during scoping and flag any Standard-tier accounts that contain deal records as tier-unavailable rather than migrating. The dealstage property maps to Opportunity StageName, and pipeline assignment maps to a Sales Process or Record Type that we configure before migration. Closed-won and closed-lost outcomes from Firmao become Dynamics Stage values with probability percentages preserved.

Firmao Tasks map to Dynamics 365 Tasks with Subject, Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving Firmao owner references to Dynamics User records via email match. Firmao's subClass/subId envelope for object relationships (which Task is associated to a Contact or Deal) translates to the WhatId (regarding) reference on the Dynamics Task, resolved after Contact and Opportunity import completes.

Firmao Products map to Dynamics Product2 records. The productCode field maps to Product Number. Where Firmao products have per-warehouse stock state stored as subClass=warehouse entries (netPriceInStore, currentStoreState), we extract each subId variant as a separate warehouse location and recreate them as custom fields or related records in Dynamics depending on whether the destination org includes the Inventory and Warehouse Management module. Base product pricing migrates to the Standard Price Book.

Firmao Users (name, email, role) map to Dynamics 365 User records resolved by email match. We export the complete user list and map owner assignments on Deals and Tasks. Users without a matching Dynamics User go to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive or archived Firmao users map to inactive Dynamics users to preserve historical assignment without granting active seat licenses.

Firmao custom fields use dot-notation keys (customFields.custom5) without human-readable labels in the API response. We retrieve a sample record via GET to enumerate which custom fields are populated, cross-reference with the customer's import documentation, and exclude fields with no values in the sample (potentially deleted fields). Each populated custom field is created as a typed custom attribute in the Dynamics solution before migration begins. Custom fields are gated behind Firmao Professional tier, so we confirm the active plan during scoping.

Firmao tags are stored as a comma-separated property on the Contact or Company record (no dedicated /tags endpoint exists). We extract the tag values, parse them, and create a multi-select picklist attribute in Dynamics for the relevant entity. The customer chooses whether to use a single global tag field or separate tag fields per entity (Contact Tags, Account Tags) during scoping.

Firmao Invoice records (headers and line items with VAT tax codes and payment status) map to Dynamics 365 Invoice. Invoice is a standard object in Sales Professional and above. We map line item quantity, unit price, tax code, and payment terms. Firmao invoice PDFs stored in the cloud vault are not accessible via REST API and do not migrate as blobs; we flag them for manual retrieval and re-upload to Dynamics Notes or SharePoint post-migration.

Firmao Projects (Professional+ with Gantt and Kanban) map to Dynamics 365 Project Operations if the destination license includes it, or to a custom Project entity if not. We migrate project name, description, start and end dates, and task associations. Gantt bar positions, Kanban column configuration, and visual layout data do not transfer — these are layout metadata not stored as data records. We flag these for manual rebuild or reconfiguration in the destination.