Import and export resources

Define the migration

Distinguish moving configuration resources from restoring a full installation. An entity export may not contain historical statistics, private settings, hosted files or every integration credential.

Export first

Use the source system's supported export tool and preserve the untouched original. Record its version and export options. For an API-assisted import, confirm the source account's permissions and endpoint availability.

Import into the target

1. Open Settings → Import/Export or the applicable import tool.
2. Select the source type actually offered by the current panel.
3. Provide the file or supported source connection.
4. Read the preview, warnings and available entity selections.
5. Check how domains, groups, users and references are mapped.
6. Import a limited scope first when the tool permits it.

Keep the file's actual extension and format. Renaming a file does not convert its contents.

Validate the result

Inspect imported sources, landers, offers, rules and campaign links. Confirm credentials and permissions separately. Verify a click and conversion before directing traffic to the imported setup.

Configuration exports and scheduled copies

In the configuration export section, use Run export to create a fresh copy, then download the resulting file. The current configuration import uses its supported .sql.gz file and an explicit confirmation before starting. Read the selected format rather than choosing a tool solely by a similar name.

The configuration export does not replace statistics or integrated landing-file backups. Where Auto-backup is available, enable it and set the interval in seconds. Copies stored on the same server still need an off-server backup. See backup and recovery for the complete scope.

Retry and recovery

Check which entities were created before repeating an interrupted import. Duplicate names and partially transferred references can require manual review. Keep a backup of the target as well as the original export; do not clear existing production data merely to avoid resolving a mapping conflict.