Xtrable
Contact us

Export and import

Export a simulation to a single file, commit it, share it, and import it again to get back an identical setup. The data created at runtime is deliberately left out.

A simulation's definition is portable. Export it, commit it next to your code, share it with a teammate, and import it elsewhere to get back the same stand-in.

What export contains

Export produces one document with the simulation's definition and seed: the OpenAPI document, the resources and their fields, the links between them, the settings, the auth endpoints, the seed records, and a note of whether it was imported or authored by hand.

Import rebuilds a simulation from that document, and the result is identical to the one you exported. Round tripping is a tested guarantee. You can import straight from the home screen, with no need to make an empty simulation first.

Definition and seed, not live data

Understudy keeps two things apart, because export treats them differently:

  • Definition and seed describe the simulation and its starting data. This is exported, so a shared file always stands up the same way.
  • Runtime data, the records created by API calls after it started, is not exported. It belongs to a running instance, not the definition.

So an exported file is a clean, repeatable recipe, the same for everyone who imports it.