# Assign source, destination, and orchestrator roles for Storage Migration Service

> Which migration roles and inventory decisions should be established before data transfer?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:30+00:00
- Modified: 2026-09-08T18:17:14+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

Which migration roles and inventory decisions should be established before data transfer?

## Potentially affected

Use this review when planning a Storage Migration Service project.

## DSE recommendation

Create a role map that names the machine responsible for orchestration separately from the data endpoints.

## Article

## Source facts

Storage Migration Service inventories supported Windows, Linux, and NetApp CIFS sources and transfers data to newer servers or Azure virtual machines. Microsoft distinguishes source, destination, orchestrator, and management-interface roles. For one migrating server, the destination can also orchestrate; for several, the source recommends a separate orchestrator. Identity cutover is optional and occurs after the data-transfer stage. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview).

## Applicability

Use this review when planning a Storage Migration Service project. Identify the source types, destination versions, number of servers, and management tools. Verify the complete current support requirements before including a source in the inventory.

## DSE recommendation

Create a role map that names the machine responsible for orchestration separately from the data endpoints. Have data owners review the inventory and proposed destinations before approving transfer. Record which servers need an eventual identity handoff and which need only copied data. Keep transfer acceptance and the optional cutover decision as separate milestones.

## Verification

Compare the discovered inventory with the approved source list and reconcile missing or unexpected data before copying. After an authorized transfer, inspect the recorded results and sample destination files with their owners. Preserve the role map and transfer evidence. Proceed to identity cutover only under its separately reviewed plan for the accepted endpoints.

## Official references

[Microsoft Learn: Storage Migration Service overview](https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview). Source reviewed September 8, 2026.

## Primary reference

- Name: Storage Migration Service overview
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Assign source, destination, and orchestrator roles for Storage Migration Service,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-041-assign-source-destination-and-orchestrator-roles-for-storage-migration-service/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.