Moving a configuration between tenants

Screens are configuration, and configuration should move between companies the way any other transport does. Export every design to one file, import it into another tenant, and see exactly what will happen before it happens.

1. 1

   Export the bundle

   One file holds every screen design in the company. It also carries the definitions of the user-defined objects those screens read, which is what lets the target tenant be missing them.

2. 2

   Run the preflight in the target

   Import is read-only until you say otherwise. The preflight lists collisions with existing screens, renames, references it cannot resolve and S/4 dependencies the target may not have.

3. 3

   Decide per screen

   Create, overwrite or skip — screen by screen, not all-or-nothing. A partial import is a normal outcome, not a failure.

4. 4

   Watch it run

   Progress is per screen with timings, so a long restore is legible rather than a spinner. Missing user-defined objects are created as it goes.

Back to the designer.