Correct sequence for migrating project

[K-Hamdy]

Hello,

We are migrating from Azure DevOps Services (cloud) to Azure DevOps Server (on-prem) using version 16.3.x of Azure DevOps Migration Tools.

We want to confirm the correct and officially recommended processor execution order for a full migration that includes:

• Work Items (including Test Cases & Shared Steps)
• Test Configurations
• Shared Parameters (Test Variables)
• Test Plans & Test Suites
• Area Paths & Iterations

Based on our understanding, the expected order should be:

• TfsNodeStructureMigrationProcessor (Areas & Iterations)
• TfsWorkItemMigrationProcessor (including Test Cases & Shared Steps)
• TfsTestConfigurationsMigrationProcessor
• TfsTestVariablesMigrationProcessor
• TfsTestPlansAndSuitesMigrationProcessor

We would like confirmation on the following:

Is this the correct and supported execution order?

Should Test Configurations and Test Variables always be migrated before Test Plans & Suites?

Are there any known dependencies between TestVariables and TestConfigurations?

Is it recommended to run these processors in separate executions rather than a single combined configuration?

Additionally:

Are there any known limitations when migrating Test Plans from Cloud to Azure DevOps Server?

Is there any required configuration flag for TestPlansAndSuitesMigrationProcessor when migrating cross-platform (Services → Server)?

We want to ensure we follow the officially supported sequence to avoid missing test suites or suite hierarchy issues.

Thank you in advance for the clarification.

[K-Hamdy]

@MrHinsh can you help please?

[MrHinsh]

Please see the "how-to" documentation provided.

[K-Hamdy]

thank you for your reply. but i've viewed the documentation and i'm afraid i'm a bit lost. if you can guide me on which documentation article to read at least that would be great.
thanks