Strategies to handle exceeding rate limiting thresholds

[t-anderson]

Has anyone run into the issue of rate-limiting/delayed-requests which extend migration run times?

The team I am migrating would like their migration of work items to be completed over a weekend and to be able to pick up work in the target project at the start of business the following week.

I have broken up their work items into multiple queries which can be done with multiple migration runs. However, I still run into the Azure DevOps rate limiting threshold which is causing the migration user's requests to be delayed, causing long migration run times.

Is there any guidance on how to avoid hitting rate limits or remove limits and to be able to complete this migration within a weekend?

[MrHinsh]

The rate limit is unavoidable as it protects the system and other users.

You can work through them as they only inject delays and do not stop the migration.