Blueprint Export and Import
Configuration that lives only in one place is configuration that's hard to move. Promoting a new setup from a staging environment to production. Sharing a working app configuration with another team. Backing up an app before making major structural changes. Each of these requires the ability to package configuration and deploy it somewhere else.
Blueprint export and import is that capability.
Export Everything
A blueprint export packages the complete configuration of an app: all object type definitions, all screen configurations, all navigation definitions, all workflow rules, all field definitions, all extension settings.
The export is a single file that captures the app's entire setup at a specific point in time. The file is human-readable — structured text that can be reviewed, versioned in source control, and compared across versions.
Import Anywhere
A blueprint file can be imported into any app. The import replays the configuration from the file, applying each definition to the target app.
Import into a blank app and you get the exact configuration that was exported. Import into an existing app and the definitions are merged — new definitions added, existing ones updated, definitions not in the blueprint left unchanged.
This makes promotion between environments straightforward: export from staging, import to production. The configuration moves exactly as designed, without manual reconstruction.
Version Control Friendly
Because blueprints are text files, they integrate naturally with source control tools. Store blueprint snapshots alongside your other business documentation. Track configuration changes through commit history. Compare versions to understand what changed between two states of the app.
For teams that practice configuration-as-code discipline, blueprints are the artifact that makes the workflow possible.
Before Major Changes
Blueprint export is a natural pre-change checkpoint. Before reorganizing your data model, before changing workflow rules, before restructuring navigation — export a blueprint. If the changes don't work as expected, import the blueprint to restore the previous state completely.
This is a more comprehensive safety net than per-definition revert, which operates at the individual definition level. A blueprint captures the entire app state.
Sharing Between Teams
Teams building similar apps can share blueprints. A blueprint for a customer service app, a blueprint for an order management workflow, a blueprint for an expense tracking process — these can be shared and adapted rather than rebuilt from scratch each time.
Import a shared blueprint, customize what's specific to your workflow, and build from there. The starting point is a working configuration, not a blank slate.