Data Migration in RCOM Gateway
Data migration in RCOM Gateway ensures that critical configurations, workflows, and operational data can be safely transferred across environments. Whether you’re setting up a new instance, replicating a proven configuration, or maintaining regular backups, migration tools help streamline the process and reduce risk.
RCOM Gateway supports two migration methods, each tailored to different needs:
1. Migration via XML (Import/Export)
The XML Import/Export feature provides a straightforward way to move or back up datasets.
- Export configurations and object data into an XML file.
- Import the file into another instance to restore or replicate settings.
- Ideal for quick migrations, backups, or test-to-production transfers.
2. Migration via Packages (JSON)
The Packages feature is a more advanced option designed for controlled, enterprise-grade deployments.
- Scoped, versioned exports in JSON format.
- Fine-grained selection of modules and components.
- Built-in review and side-by-side comparison before import.
- Suitable for production environments, auditable change management, and multi-role workflows.
Key Differences from XML Export/Import
| Feature | XML Import/Export | Packages |
|---|---|---|
| Format | .xml | .json |
| Permissions | Export access = Import access | Can delegate import to higher roles |
| Granularity | Full or filtered item selection | Fine-grained module/component-level selection |
| Review Before Import | ❌ No preview | ✅ Preview and compare with existing data |
| Status Workflow | ❌ None | ✅ Draft (Created) → Ready → Download/Import |
| Editable Before Finalization | ❌ | ✅ |
| Auditability | ❌ | ✅ Scoped, versioned package with metadata |
Which Method Should You Use?
- Use XML Import/Export if you need fast and simple transfers or backups.
- Use Packages if you require version control, auditability, or staged deployments in production.
Both methods complement each other — XML for speed and convenience, Packages for security and governance.