Use a mission export to move its structure or keep a configuration snapshot. Keep account credentials and customer documents outside the export.

​
Export a mission

Open the mission’s menu and choose the export action available in your build. Name the file with the purpose, version and date so a reviewer can distinguish it from other configurations. Inspect the file before sharing it. Step text can contain URLs, headers, sample values and other information you pasted directly into the builder. A connection reference does not imply all sensitive content has been removed.

​
Import

Open Missions and use Import. Choose the exported configuration, then inspect the trigger and each action. Reconnect accounts, choose resources and check gadget versions before testing. Do not enable an imported mission until you have checked its live trigger and destinations. Test with fresh sample IDs so its results are distinguishable from earlier runs.

​
Organize

Name missions by outcome and use folders where available. Keep related missions and tables together. Separate practice missions from work that is enabled for live events. Exports are not a complete database backup. Operators should also back up the database, file storage, encryption keys and deployment configuration. See backup and rollback.