Use the versioned profile package
The current profile export carries app identity, app-link configuration, deep links, text and URL share-fixture content, file-fixture metadata, scenarios, notification templates, and non-secret push-setup metadata in a versioned JSON package.
It is intended for reproducible setup, not for backing up credentials, push logs, or scenario evidence files.
Understand what stays behind
Provider credentials, sensitive target-token values, secure-store references, push delivery logs, and share-fixture file contents are deliberately omitted. Imported file fixtures retain their name and type metadata but require the local file to be selected again.
Removing secrets and files from the package prevents an import file from becoming a portable credential or document store.
Import and restore locally
Review the incoming profile, then import it on the destination device. Imported push setups remain disabled until the required token and provider credential are restored through secure storage.
Open representative deep links and review profile identifiers before relying on imported scenarios.
Retire stale data
Archive or remove profiles that no longer represent an installed app or active test target. Delete transfer packages once they are no longer needed, because app identifiers, routes, and test names may still be sensitive.
Deleting an export does not delete the local profile, and deleting a profile should also remove its associated secure values after confirmation.