Horizontal strategy for SAP Migration

This is a common challenge in horizontal migrations, especially when DEV and QAS are temporarily split across environments.

In most real scenarios, teams avoid relying on a single shared transport directory during the transition. Instead, they use a temporary dual transport setup.

Typically, teams configure separate transport directories for on-prem and Azure systems, use transport routes carefully, and control movement between landscapes. Transports are synchronized using tools like CTS+ or manual import and export where needed.

Another approach is to migrate DEV and QAS as close together as possible to reduce the duration of a split landscape.

Also, strict transport governance becomes critical during this phase. Without it, inconsistencies happen quickly.

In practice, a full transport freeze is rarely feasible, so controlled transport movement with clear tracking is the safer approach.