Export and import
Export and import move an app blueprint (the recipe), not a full customer workspace. Use them for backups, moving between environments, or sharing a starting blueprint.What travels
Exact bundles evolve with the product; treat this as the operating contract: recipe yes, customer data no.
Export from App Settings is recorded in App Settings → Privacy → Access log (who exported, and whether the app was under a signed BAA). If that record cannot be written, the download is refused.
For an app after the BAA is accepted, the owner and app admins can still export a backup. GenieForge staff cannot download that blueprint. The file omits test suite source and decision write-ups (titles stay). Re-importing that file skips empty tests and still recreates decision titles.
Import needs a current export. If an older backup file is refused, export the app again from a current copy and import that file.
Export from App Settings. Import from your apps home (where you create and open apps). You do not need a special Build prompt unless you want help preparing the app before export (“make sure Build Rules capture our naming conventions before I export”).
After import into a fresh app or environment:
- Open App Blueprint and confirm pages, roles, and automations you expect.
- Select a project, Preview as a key role, and smoke-test the critical path.
- Re-enter secrets under Environment Variables in the destination.
- Reconnect OAuth / connected accounts as needed.
- Re-invite your team from App Settings and re-verify any notification email addresses (these never travel with an export).
- Re-publish public intake if you use it: you get a new URL and QR (re-download or re-print). Brand colors from App Settings transfer; project branding overrides do not.