Migrate Gateway
Data migration moves Gateway configuration between environments and can be used to reproduce a tested setup, transfer a controlled change, or restore selected data. R-COM Gateway provides two migration paths. The right path depends on whether the migration needs a dependency check and preview before it changes the target Gateway.
Choose a Migration Method
Use Configuration Migration for the current package-based workflow. It creates a ZIP export, checks dependencies, and creates an import preview before configuration is applied.
Use Import / Export (Legacy) when an XML transfer is required. The legacy workflow exports XML and imports it directly; it does not provide the package dependency check or import preview available in Configuration Migration.
| Feature | Configuration Migration | Import / Export (Legacy) |
|---|---|---|
| Navigation | Data Migration > Exports and Imports | Data Migration > Legacy Import / Export |
| Export file | ZIP package | XML file |
| Selection | Selected configuration types and items | Full or filtered item selection |
| Dependency check | Yes. Review required configuration before download. | No. |
| Import preview | Yes. Review proposed changes before starting the import. | No. The XML import is applied directly. |
| Result review | Import-job results and downloadable reports. | Import log and post-import verification. |
Configuration Migration
Configuration Migration uses two linked job lists: Exports on the source Gateway and Imports on the target Gateway. It is the recommended path when you need to understand what will be transferred before the target Gateway is changed.
How It Works
- In Exports, create an export job and select the configuration types and items to transfer.
- Review the dependency check. Add required dependencies before the package is downloaded.
- When the export is Ready to download, download the ZIP package and, if needed, the validation report.
- In Imports on the target Gateway, upload the ZIP package and create an import job.
- Review the import preview, validation results, and workflow activation changes. Rebuild the preview after changing the import-job selection.
- Start the import only after the preview is acceptable, then review the job results and reports.
The export and import lists retain the jobs created in each Gateway. This lets you return to a job while it is waiting for review and review its final state after it has completed, been cancelled, or failed.
Use Configuration Migration for controlled test-to-staging or staging-to-production changes. Create focused export packages so that the dependency review and import preview remain easy to verify.
Read the detailed guides for the available actions, statuses, and result handling:
Import / Export (Legacy)
Import / Export (Legacy) is the XML-based migration workflow. It is useful when an XML export or import is required for an existing process.
The legacy workflow has two direct operations:
- Select configuration or object data and export it as an XML file.
- Upload the XML file in the target Gateway to apply the included configuration.
Because the XML workflow does not provide an import preview or package dependency check, review the scope of the XML export carefully and verify the target Gateway after import. Use the Import Log to identify errors or warnings.
Read Import / Export (Legacy) for XML selection, upload, and post-import verification steps.
Plan a Migration
Before migrating configuration:
- Identify the source and target Gateway and the configuration change that must be transferred.
- For Configuration Migration, use a meaningful export or import name and description so that the job can be identified later.
- For Configuration Migration, review dependencies during export and the preview before starting import.
- Test production-bound changes in an appropriate non-production Gateway before applying them to production.
- Review the completed import results or legacy import log, then verify the affected configuration in the target Gateway.