Migrate from Field2Base to Microsoft Dynamics 365 Sales

Field2Base Companies map 1:1 to Dynamics 365 Accounts using direct field mapping. Company name, address, phone, fax, and website transfer as standard Account fields with identical or closely matched names. Parent-child company hierarchies in Field2Base map to the Account.ParentAccountId lookup field, which requires parent companies to load before child records to satisfy the foreign-key constraint. We export the full company roster first and sequence the load accordingly.

Field2Base Users who are internal staff members map directly to Contacts in Dynamics 365 and receive user licenses as appropriate. External stakeholders such as subcontractors, third-party submitter emails, and field workers who only submit forms become Contact records without Dynamics 365 user licenses. OwnerId assignment on migrated records requires Azure AD user matching by email — the submitting user's email address is resolved against Azure AD to populate the OwnerId field on the corresponding Note or custom table row.

Each Field2Base form submission becomes a Note (annotation) attached to the corresponding Account or Contact record. The note body contains a formatted summary of all region values and metadata (submission date, submitting user, GPS coordinates). This preserves the submission record without forcing a custom table for simple form data.

For form templates with high business value (inspection results, safety checklists, work orders), FlitStack creates a custom Dataverse table named after the form template. Each submission becomes a row in that table, with region values as columns. The custom table links to the Account or Contact via a lookup field.

Field2Base Region types map to Dataverse column types: Text regions become Single-Line Text or Multi-Line Text, numeric regions become Decimal or Whole Number, drop-down regions become Choice columns, date regions become Date Only or DateTime columns, photo regions become Image columns or SharePoint file attachments, GPS regions become two Decimal columns for latitude and longitude, signature regions become Image columns.

Field2Base regions with calculated values or conditional visibility logic do not transfer as live formulas. The calculated result is stored as a static value in the migrated record. If the calculation logic must persist dynamically, it is documented and rebuilt as a Power Automate cloud flow or Dataverse calculated column post-migration.

Field2Base Workflow definitions (one-step review, multi-user approval routing, edit-before-submit logic) do not have a Dynamics 365 equivalent that accepts direct migration. We export the workflow definition as a reference document. Power Automate handles equivalent logic in Dynamics 365, including Teams notifications, approval emails, and conditional record updates.

Photos attached to Field2Base form submissions are downloaded and re-hosted. For organizations with SharePoint integration enabled, files upload to the Account's SharePoint document location. Without SharePoint, photos attach as notes to the Dynamics 365 record. File size limits on Dynamics 365 annotations (30MB per file) apply.

Field2Base signature regions export as PNG images. These upload as image columns in custom Dataverse tables or attach as files to the parent record. The original signing user's email and timestamp are preserved in the record metadata for audit continuity.

GPS coordinates, device model, and offline/online submission mode from Field2Base metadata transfer as custom columns on the target Dynamics 365 record or custom Dataverse table. We create Location__c (two-decimal columns) and DeviceInfo__c text columns for this data. Original submission timestamps are preserved in the CreatedOn field or a custom SubmissionTimestamp__c datetime column.

Field2Base role definitions (Form Designer, Mobile User, Admin) have no direct equivalent in Dynamics 365 Security Roles. We document the role-to-role mapping as a reference for your Dynamics 365 admin to assign appropriate security roles post-migration. Active Directory group synchronization via Azure AD is recommended for ongoing provisioning.

Field2Base Data Integration Module connections to back-end SQL, ODBC, or OLEDB data sources do not migrate. These are documented as reference. Rebuilt connections to source ERP or SQL systems use Power Platform connectors (SQL Server, ODATA) or Azure Data Factory pipelines post-migration.