Migrate to WSO2 Integrator
WSO2 Integrator provides migration tools to help you move existing integrations from other platforms to WSO2 Integrator. The tools analyze your integration artifacts, generate equivalent Ballerina code, and produce a migration report highlighting items that require manual attention.
If you're moving an existing integration platform to WSO2 Integrator, start with the page for your current platform. Each page covers running the migration tool (every wizard screen and CLI flag), handling items that need manual attention, how platform concepts map to their WSO2 Integrator equivalents, and worked examples.
Choose your platform
Migrate from MuleSoft
- Wizard or CLI, rule-based or AI-powered
- Concept mapping and worked examples
Migrate from TIBCO BusinessWorks
- Wizard or CLI, rule-based or AI-powered
- Concept mapping and worked examples
Migrate from Azure Logic Apps
- CLI-only, AI-powered
- Concept mapping and worked examples
Supported platforms and features
| Source platform | WSO2 Integrator wizard | CLI | Rule-based | AI-powered |
|---|---|---|---|---|
| MuleSoft | ✓ | ✓ | ✓ | ✓ (optional, currently not available in CLI) |
| TIBCO BusinessWorks | ✓ | ✓ | ✓ | ✓ (optional, currently not available in CLI) |
| Azure Logic Apps | ✗ | ✓ | ✗ | ✓ (mandatory) |
Legend:
- WSO2 Integrator wizard: Migration supported via the WSO2 Integrator migration wizard UI.
- CLI: Migration supported via the Ballerina CLI tool.
- Rule-based: Deterministic, rules-driven migration (non-AI). Available for MuleSoft and TIBCO only.
- AI-powered: Migration uses AI. For MuleSoft and TIBCO, this is an optional enhancement (currently only available in the WSO2 Integrator wizard, not the CLI). For Logic Apps, migration is performed entirely by AI and is mandatory.
Migration workflow
Migration can be initiated using either the WSO2 Integrator migration wizard (UI, where available) or the CLI tool. The table above shows the capabilities supported for each platform.
After migration, complete the following post-migration steps:
- Review: Check the migration report to understand what was done during migration and identify any items that need manual attention.
- Implement: Complete any manually flagged items (custom logic, complex transformations, or unsupported elements).
- Configure: Set up
Config.tomlwith connection details and environment-specific values. - Test: Review any auto-migrated tests, and add or update tests as needed to ensure the migrated integration behaves as expected compared to the source system.
- Deploy: Deploy to WSO2 Integrator.
Command reference
| Command | Description |
|---|---|
bal migrate-mule <source-project-directory-or-file> | Migrate from MuleSoft |
bal migrate-tibco <source-project-directory-or-file> | Migrate from TIBCO BusinessWorks |
bal migrate-logicapps <source-project-directory-or-file> | Migrate from Azure Logic Apps |
-o, --out <output-directory> | Output directory of the migration |
-v, --verbose | Enable verbose output |
-m, --multi-root | (MuleSoft/TIBCO) Treat each child directory as a separate project and convert each. (Logic Apps) Treat each JSON file in the directory as a separate project and convert each. |
-d, --dry-run | (MuleSoft/TIBCO) Analyze and generate a migration report without generating Ballerina code |
-k, --keep-structure | (MuleSoft/TIBCO) Preserve original project structure |
Don't see your platform listed? The same underlying concepts — services, connectors, data transformation, error handling — carry over regardless of where you're migrating from. Get started with WSO2 Integrator directly, or reach out on Discord for migration guidance specific to your platform.