What to expect when migrating from VSA9 to DRMM with EDR

VSA 9 users are migrating to DRMM ahead of the product's end-of-life in August 2027. As part of this transition, many organizations may want to integrate their existing EDR instance with DRMM.

IMPORTANT  The current recommendation is to delay setting up the EDR-DRMM integration until Q4 2026.

How the EDR-DRMM integration currently works

When you connect an existing EDR instance to DRMM, the integration automatically:

  • Creates new EDR locations mapped to your DRMM sites.
  • Associates devices to those newly created locations.

Current limitation: Existing EDR locations cannot be mapped to DRMM sites. As a result, devices are moved to newly created locations instead of remaining in their current EDR locations.

Why this is disruptive

Devices that move to new locations inherit the security policies and exclusions associated with those locations. Unintended policy changes can result in:

  • Quarantining of business-critical systems.
  • Endpoint isolation.
  • Loss of custom exclusions configured for your environment.

What's coming in Q4 2026

EDR will introduce a new DRMM integration flow that allows you to:

  • Map your existing EDR locations to their corresponding DRMM sites.
  • Prevent automatic creation of new locations.
  • Prevent devices from moving across locations during integration.
  • Maintain current policies and exclusions without disruption.

Recommendation

Wait for the Q4 2026 integration update before connecting your EDR instance to DRMM. If you proceed with the integration today, be aware that devices will move to auto-created locations and may inherit different policies.

If you have questions or need guidance, contact support.

FAQ after the Q4 2026 integration update

No. Device groups are created and managed in Datto EDR and are not mapped to DRMM device groups.

Existing device groups remain unchanged.

No.

After you map your existing EDR locations to the corresponding DRMM sites, the locations remain associated with their current organizations and policies.

Unmapped locations remain unchanged.

However, if a device in an unmapped location has an RMM agent installed, EDR attempts to identify the corresponding synced location and automatically moves the device. Plan location mappings carefully to avoid unintended device movement.

Any DRMM site that is not mapped is automatically created as a synced location in EDR and assigned to the Default RMM organization.

Devices placed in that organization inherit any policies assigned to it.

NOTE  The Default RMM organization cannot be permanently deleted. If it is removed, it is recreated the next time the integration generates a new location.

Yes. If a location exists in EDR but not in DRMM, and the corresponding site is later created in DRMM, the integration creates a new location in EDR, resulting in duplicate locations.

Use the Q4 location-mapping workflow to align existing locations before this occurs.

No. Device moves must be performed in DRMM.

After moving a device to a new site in DRMM, restart the endpoint to synchronize the change with EDR.

See Integration: RMM & EDR.

 

   

Initial release.

8/24/26