Edit

Migrate Field Service to a new environment

When you move, copy, or restore the Power Platform environment that hosts Dynamics 365 Field Service, what transfers depends on the selected platform operation. A tenant-to-tenant move, restore, or Everything copy includes solutions and Dataverse data. A Customizations and schemas only copy doesn't include application data. After any migration, validate Field Service components that depend on environment-specific connections, Azure resources, or configuration.

Use this article together with the platform migration guidance. It summarizes Field Service validation and links to platform procedures for dependencies such as Power Apps, Power Automate, and Azure Synapse Link for Dataverse. For a first-time installation in a new environment, go to Install Dynamics 365 Field Service.

Prerequisites

  • You have the administrative permissions required for the selected platform operation. For example, an environment copy requires the Environment Admin or Dataverse System Administrator role. A tenant-to-tenant move requires Power Platform or Dynamics 365 service-administrator privileges. Use the Dataverse System Administrator role to validate and configure the destination environment.
  • You completed the platform-level move by using the appropriate Power Platform process:
  • You reviewed your overall environment strategy and application lifecycle management (ALM) checklist before you migrate.

What carries over and what you reconfigure

A tenant-to-tenant move, restore, or Everything copy includes solutions and Dataverse data, including configuration and transactional records. A Customizations and schemas only copy includes users, customizations, and schemas, but not application data. Components outside solutions, such as connections and some flows, might also require manual attention after a copy.

For operations that include Dataverse data, the following items normally carry over:

  • Field Service solutions and customizations
  • Configuration data, such as settings, incident types, price lists, and tax codes
  • Transactional data, such as work orders, bookings, and assets
  • Security role definitions

Validate the following items in the destination environment:

  • Connection references, connections, and required cloud flows
  • Resource Scheduling Optimization add-on installation and optimization configuration, if used
  • Maps, geocoding, and location settings
  • Mobile offline profiles, app associations, filters, and assignments
  • Dual-write, Internet of Things (IoT), Azure Synapse Link, and mailbox connections, if used
  • User mapping, security groups, and record ownership for tenant-to-tenant moves

For a Customizations and schemas only copy or a new destination environment, transfer the required Field Service configuration data separately. Learn more about transferring configuration data in Move Field Service configuration data.

Move Field Service configuration data

If your destination is a new environment rather than a full copy or move, use the Configuration Migration tool to transfer Field Service configuration and reference data between environments. This tool supports customer engagement apps, including Field Service. Examples of configuration data include Field Service Settings, incident types, priorities, work order types, tax codes, price lists, and service task types.

When you use the tool, keep these points in mind:

  • The tool moves configuration and reference data, not end-user transactional data such as accounts, contacts, or work orders.
  • If Field Service business logic could affect the imported records, select Disable plug-ins in the export schema. Include this option only when it's needed for the data set, and validate the affected business logic after the import finishes.
  • The tool doesn't migrate the Calendar table or image columns, so work hours, calendars, and inspection images need a separate approach.
  • Import into a preproduction environment first, and back up the destination environment before you migrate.

Reconfigure Field Service after migration

After the migration finishes, reconfigure or validate the following Field Service components in the destination environment.

Connection references and cloud flows

Field Service uses Power Automate cloud flows for features such as work order recap, booking alerts, and inspections. Connection references are environment-specific and can use connections that their owners share with you. After migration:

  1. In Power Apps, select Solutions and open the Default Solution to inventory the connection references in the destination environment.
  2. Review the Field Service managed and add-on solutions for additional connection references.
  3. Associate each required connection reference with a valid destination-environment connection.
  4. Identify the cloud flows disabled by the selected copy or import operation and turn on only the flows required in the destination environment. Before you enable a flow, confirm that you have the required license, privileges, and permission to use its connections.

For a tenant-to-tenant move, complete the platform's post-migration process for Power Automate. It includes mapping connection references, enabling child flows before parent flows, and updating trigger URLs. If you migrate a custom connector, review the custom connector solution limitations before you import dependent connection references and flows.

Learn more about connection references in Use a connection reference in a solution and about solution lifecycle management in Application lifecycle management (ALM) basics.

Power Apps and custom pages

For a tenant-to-tenant move, follow the platform's Power Apps preparation and post-migration steps. Solution-aware canvas apps, custom pages, and component libraries stop working after the move unless you export and remove them from the source environment first, and then import them into the destination environment.

Learn more in Prepare Power Apps for a tenant-to-tenant migration and Complete the post-migration process for Power Apps.

Maps, geocoding, and location settings

After migration, validate the following location settings:

  • In the Resource Scheduling app, go to Settings > Administration > Scheduling Parameters and confirm that Connect to Maps has the intended value.
  • In Field Service Settings, confirm that Auto Geo Code Addresses has the intended value.
  • Test address resolution. Regeocode affected records only if their location data doesn't resolve correctly.

Learn more about these settings in Set up maps, geocoding, and routing.

Resource Scheduling Optimization add-on

If you use the Resource Scheduling Optimization (RSO) add-on, validate it in the destination environment.

Steps 2 through 5 apply only to an operation that includes Dataverse data: a tenant-to-tenant move, a restore, or an Everything copy. A Customizations and schemas only copy brings the add-on but not the optimization scopes, schedules, objectives, and goals. Create those in the destination environment or transfer them as configuration data, then complete steps 2 through 5.

  1. Confirm the Resource Scheduling Optimization add-on is present. In the Power Platform admin center, select Manage > Environments, select your environment, and then select Dynamics 365 apps. The copied add-on normally shows as Installed. If it isn't listed, select Install app, and then select Resource Scheduling Optimization.

    Important

    Installed doesn't mean the add-on is ready to run. Copied schedules can still fail. Complete the remaining steps before relying on it.

  2. Confirm the expected optimization scopes, schedules, objectives, and goals are present and correctly configured.

  3. Re-publish each optimization schedule that's already in a Published state. Copied schedules keep their published status but don't run in the destination environment until they're published there.

    Note

    Leave unpublished schedules as they are. Publishing one starts an optimization that the source environment wasn't running.

  4. Confirm each re-published schedule shows a next run time. If its recurrence date range has ended, there is no next occurrence; the field can be empty or show a past time. Extend the date range if the schedule should run again.

  5. Run a test optimization and confirm it produces bookings.

Resource Scheduling Optimization runs as a Microsoft-managed service. There are no environment-specific Azure resources or keys for you to repair after a migration.

Learn more in Deploy the Resource Scheduling Optimization add-on.

Note

The add-on license allows for unlimited use of schedule optimization, whether on a regular cadence or ad hoc basis. The license includes one active instance of Resource Scheduling Optimization per tenant.

For purchasing guidance, including additional licenses for the copied environment, see Get Resource Scheduling Optimization.

Mobile offline profiles

The Field Service mobile app uses offline profiles to sync data to frontline workers' devices. If you use mobile offline, validate the configuration before asking frontline workers to use the destination environment:

  1. Confirm the mobile offline profile and its entity filters exist in the destination environment.
  2. Confirm that the profile is published, associated with the Field Service Mobile app, and assigned to the appropriate users or teams.
  3. If you change the profile or its assignments, publish the profile.
  4. Ask a test user to sign in to the destination environment and complete a full sync.

Learn more in Set up the mobile offline profile. If the app connects to the wrong environment, go to Troubleshoot common issues in the Field Service mobile app.

Integrations

Validate the integrations used by the destination environment:

  • Dynamics 365 finance and operations apps (dual-write): Integrations with finance and operations apps, such as Dynamics 365 Finance and Dynamics 365 Supply Chain Management, use dual-write. For a copy or restore, follow the official unlink, environment-cleanup, and relink procedure before you reenable the required table maps. A Dataverse organization linked to a finance and operations apps environment can't be migrated to a different tenant, and cross-tenant links aren't supported. Plan a different approach if you need to move a linked environment. Learn more about copy and restore scenarios in Unlink and relink dual-write environments and about the tenant-move restriction in Tenant-to-tenant migrations.
  • Project Operations: Field Service and Project Operations are Dataverse apps, so their integration moves with the environment. After migration, validate the integration's recurring Power Automate flow and its connection. If the deployment also connects to finance and operations apps, such as Dynamics 365 Finance or Dynamics 365 Supply Chain Management, the dual-write rules in the previous bullet apply, including the tenant-move restriction. Learn more in Field Service integration with Project Operations.
  • Connected Field Service (IoT): Validate the IoT provider and default-provider selection, endpoint and SAS configuration, Dataverse application programming interface (API) connection authorization, and relevant Azure deployment jobs. Reconnect or redeploy components only when validation identifies a missing or invalid dependency. Learn more about these dependencies in Connected Field Service overview.
  • Azure Synapse Link for Dataverse: A tenant-to-tenant move deletes Azure Synapse Link profiles and stops data synchronization. A copy or restore doesn't include the profiles. Review how environment lifecycle events affect Azure Synapse Link, and then transport and verify the link configuration.
  • Business Central: The Business Central integration connects through a Dataverse connection and the synchronization engine, not dual-write. After a copy or tenant move, reconfigure the connection on the Dynamics 365 Connection Setup page in Business Central, select Redeploy Integration Solution to reset permissions, and run a full synchronization. After a tenant move, confirm that user email addresses match the destination Dataverse tenant so that resource mappings resolve. Learn more in Integrate Business Central with Field Service.
  • Microsoft Outlook integration: After an environment copy, mailbox synchronization can remain intentionally disabled. Enable it only if the destination is the environment that should synchronize with Exchange. Before enabling it, validate the server profile, approve the mailbox, and select Test & Enable Mailbox. Learn more about the one-environment synchronization limitation in Integrate Field Service bookings with Outlook calendars.

Users and security roles

For a tenant-to-tenant move, prepare and validate users as part of the platform migration process:

  1. Before the move, create the required users in the destination tenant, assign their licenses, and ensure they're active and authorized.
  2. Create, upload, and validate the case-sensitive usermapping.csv file required by the tenant-migration process. Application users aren't supported in the mapping file, so create them in the destination tenant.
  3. Update the destination environment's security-group membership because security groups aren't migrated.
  4. After the move, confirm that mapped users are enabled and have the required Field Service security roles and column-level security profiles.
  5. Validate record ownership and Bookable Resource associations. Reassign only records or resources associated with an unmapped or incorrect user.

Learn more about user preparation and mapping in Tenant-to-tenant migrations and about Field Service access in Set up users, licenses, and security roles.

Post-migration validation checklist

Before you route users to the destination environment, confirm the following items:

Area What to verify
Field Service apps The Field Service and Field Service Mobile apps open and load without errors.
Power Apps and custom pages Required canvas apps, custom pages, and component libraries are available and work correctly.
Connections and cloud flows Every Field Service connection reference resolves to a valid connection, and required cloud flows are turned on.
Work orders You can create, schedule, and save a work order end to end.
Schedule board The schedule board loads and shows bookable resources.
Maps and geocoding Addresses geocode and resolve correctly.
RSO add-on (if used) Previously published optimization schedules are re-published and, where their date range is still current, show a next run time. A test optimization runs successfully.
Mobile offline (if used) The mobile app signs in to the correct environment and completes a full sync.
Integrations (if used) Dual-write, Project Operations, Business Central, IoT, Azure Synapse Link, and Outlook integrations work as intended.
Users and security Users have the correct Field Service security roles and can access their records.

Troubleshoot migration issues

  • Last updated on