Migrate from Formitize to Microsoft Dynamics 365 Sales

Formitize Client maps directly to Dynamics 365 Account. The Client name becomes Account.Name; billing address maps to Address fields; website/domain maps to Website field. Parent-child Client hierarchies map to Account.ParentAccountId where present. Multi-location Clients map as separate Account records linked by the parent field.

Formitize Contact maps 1:1 to Dynamics 365 Contact. Each Contact requires an AccountId lookup to its parent Client (resolved as Account). Name, email, phone, job title, and address fields map directly. Formitize Contact custom variables migrate as Dataverse custom columns on the Contact table.

Formitize Job is the core commercial record in Formitize but has no direct Dynamics 365 equivalent—it's a blend of Opportunity and Case. We translate Job.name or Job.reference to Opportunity.Name, Job.amount or total line items to Opportunity.Amount, Job.status to Opportunity.StageName via value mapping, and Job.closedate to Opportunity.CloseDate. If Jobs are service-only with no sales value, they map to the Case entity instead.

Jobs that contain no commercial amount, invoice, or quote data—purely service or compliance records—are identified by Formitize Job Type and routed to Dynamics 365 Case (Incident) instead of Opportunity. The Case.Title receives the Job name; Case.AccountId links to the Account. Cases are routed by Formitize priority using Dynamics 365 Case Type and Priority Option Sets.

Formitize Asset maps to Dynamics 365 Asset (field-service entity) when the destination includes Field Service. For Sales-only deployments, Asset data migrates as a custom table (new_asset) in Dataverse with fields for name, client/account link, location zone, GPS coordinates (as custom lat/long columns), and custom attribute columns mirroring Formitize Asset custom fields.

Formitize Smart Tables are arbitrary data grids exported from Formitize's reporting module. Each Smart Table becomes a custom Dataverse table. Column headers map as table columns with appropriate Dataverse data types (string, integer, decimal, datetime, boolean, OptionSet). Lookup columns in Smart Tables resolve to corresponding Account or Contact records by key field matching.

Formitize Contact Custom Variables—user-defined fields on Contacts such as birthday, client_rating, or referral_source—migrate as Dataverse custom columns on the Contact table. Each variable becomes a column with the type closest to its Formitize data type (text → string, number → integer or decimal, date → datetime). The exact column names are sourced from the Formitize Custom Fields API export.

Client-level custom variables (industry_pack extensions, billing tier, zone assignments) migrate as Dataverse custom columns on the Account table. Zone-related variables may map to Option Set values if zone lists are finite, or remain as free-text custom columns for manual categorization in Dynamics 365.

Formitize Documents attached to Jobs, Clients, or Contacts are downloaded from Formitize storage and re-uploaded as Dynamics 365 Note records with file attachments. Document titles become Note.Subject; the attachment binary re-stored under Note.Body or as a SharePoint-connected file if the destination tenant has SharePoint integration enabled.

Formitize Users are matched to Dynamics 365 Users by email address. Unmatched users are flagged before migration; the destination admin either creates the user in Dynamics 365 first or assigns their records to a fallback owner. This resolution runs before any record insert to satisfy Dynamics 365 OwnerId NOT NULL constraint.

Formitize Quotes and Invoices associated with Jobs migrate as Dynamics 365 Quotes and SalesOrders linked to the corresponding Opportunity (mapped from the Job). Line items translate to QuoteDetail and SalesOrderDetail records. Invoice status and totals map to the respective Dynamics 365 entity fields. Outstanding invoice amounts and balances become custom financial fields on the Order.

Formitize Workflows (multi-stage compliance and process automation) have no migration path to Dynamics 365. The workflow definitions, triggers, and stage configurations cannot be exported from Formitize's API. We provide a Workflow Export Summary document listing every active Formitize workflow by name, trigger type, and stages so your Dynamics 365 admin can recreate them in Power Automate from scratch.