Migrate from Formaloo to Microsoft Dynamics 365 Sales

Each Formaloo Form maps to a new Dataverse custom entity in Microsoft Dynamics 365 Sales . The Form's field structure is converted to Dataverse columns with matching data types (text to SingleLineOfText, number to Whole Number or Decimal, email to Email, phone to Phone, date to Date and Time). The Form name becomes the entity DisplayName and logical name. This entity is created in the destination Dynamics environment before any Response data is migrated, as it defines the target schema.

Each Formaloo Form Response maps to one Dataverse record in the corresponding custom entity. The Response submission timestamp maps to the createdon field, and the submitter's email and metadata map to custom fields on the record. We use the Dynamics Dataverse Web API to batch-insert records with rate-limit handling and exponential backoff. Responses are imported in reverse-chronological order so that the most recent records land first for visibility during validation.

Choice fields in Formaloo map to Dataverse choice columns (OptionSet) with the same label-value pairs preserved. Rating fields (stars, NPS scale) map to Whole Number. Calculation fields cannot be migrated as live formulas since Formaloo's calculation engine does not export; we compute the calculation value at migration time and write it as a static number field, documenting the original formula for the customer's admin to rebuild as a computed column in Power Apps if needed.

Formaloo's relational Database links one Form's Responses to another Form's Responses via reference fields. We resolve each reference by querying the target Form's Responses to find the matching record (by a unique identifier field such as email or a custom ID), then write the resolved parent record GUID as a Dataverse Lookup column. Circular or multi-level references are resolved iteratively, starting from the root Form with no inbound links.

Formaloo file upload fields on Forms store attachments that migrate to SharePoint document libraries linked to the Dynamics record via SharePoint Document Location entities, or as Note attachments (annotation records) for smaller files. The choice between SharePoint and Notes depends on file size and the customer's SharePoint licensing. We preserve the original filename and the upload timestamp.

Formaloo Workspaces act as organizational containers for Forms and team members. We map Workspace membership to Microsoft Teams membership in the destination environment. If the customer prefers a lighter-weight tagging approach, Workspace names become tags on the Dynamics records that the customer's admin can filter in Views.

Formaloo folder paths (Workspace > Folder > Subfolder) are preserved as a concatenated tag string or a custom text field on each migrated record. The folder hierarchy is not reproduced as a native Dynamics structure because Microsoft Dynamics 365 Sales does not have an equivalent folder hierarchy for CRM records.

Formaloo's conditional logic, field visibility rules, and calculation formulas are UI-defined automation that does not export as structured data. We document every Logic Rule configuration as a written summary listing the triggering field, conditions, and actions for the customer's admin to rebuild in Power Automate or Dynamics business rules post-migration.

Formaloo integrations with Google Sheets, Wix, Pabbly, and webhooks are Formaloo-specific credentials and sync configurations that do not transfer to Microsoft Dynamics 365 Sales . We document each active integration as a written handoff listing the integration name, trigger/action logic, and the recommended Dynamics or Power Automate equivalent. The customer configures the new integrations post-migration.