Migrate from Workiz to Microsoft Dynamics 365 Sales

Workiz Job has no native Dynamics 365 Sales equivalent—custom Dataverse table required

Workiz organizes its entire data model around the Job object: scheduling, technician assignment, GPS tracking, job type, status, and line items all live on or relate to the Job record. Dynamics 365 Sales has no native field service job entity. Migration requires creating a custom Job table in Dataverse, which is supported in Sales Enterprise and Premium but not in Sales Professional (which limits custom tables to 15). If you hold a Professional license, you must either upgrade to Enterprise or accept that Jobs will store as Opportunities with a custom job type field, sacrificing scheduling granularity. We deliver the Dataverse table schema as part of the migration plan so your admin can pre-create it before data lands.

Workiz Automations cannot migrate to Dynamics 365—no lift-and-shift path exists

Workiz Automations are platform-specific rules with triggers, conditions (AND/OR logic), and actions that execute within the Workiz context. Dynamics 365 Sales has no built-in automation engine; workflows require Power Automate, which is a separate product with its own licensing, triggers, and connector model. There is no export format that converts Workiz automation JSON into Power Automate flows. FlitStack AI exports your automation definitions as a rebuild reference document, but every automation must be manually reconstructed in Power Automate by your admin or a consultant. This is the most significant manual work item in a Workiz-to-Dynamics 365 migration.

Workiz GPS and service area data has no destination in Dynamics 365 Sales

Workiz tracks technician GPS location and lets admins define service area polygons on a map, assigning technicians to specific geographic zones. Dynamics 365 Sales does not store geographic service area definitions or technician location data. GPS history, availability labels, and service area assignments cannot be migrated to any native Dynamics 365 field. If you plan to adopt Dynamics 365 Field Service later, the service area and routing configuration must be rebuilt from scratch using the Field Service scheduling canvas. We document your current Workiz service area settings as a CSV export for reference, but they do not transfer into the CRM data model.

Dynamics 365 Sales Professional caps custom tables at 15—may block full Workiz schema

If your Dynamics 365 environment is licensed at the Sales Professional tier, Dataverse limits you to 15 custom tables. A typical Workiz migration may require more than 15 custom objects: a Job table, Job Status History table, Job Line Items table, and custom fields on Account/Contact already consume several slots. Professional-tier customers upgrading to Enterprise unlock unlimited custom tables. We audit your target Dynamics environment before migration to confirm available table capacity and flag whether an Enterprise license upgrade is required before migration proceeds.

Workiz file attachments migrate to SharePoint—requires Dataverse SharePoint integration enabled

Workiz stores files attached to Jobs and Clients (photos, signatures, documents). Dynamics 365 Sales stores record attachments in SharePoint Online linked via Dataverse. Migrating Workiz files requires the Dataverse SharePoint integration to be enabled and configured in your Dynamics 365 environment before migration. If SharePoint integration is not set up, files cannot attach to records and must be stored as notes (with size limitations) or delivered as a bulk file package separate from the CRM. We include SharePoint integration validation in the pre-migration checklist.