MigrationAgents

Migration Agents

Migration Agents streamline the process of migrating applications and integrations to MuleSoft. These agents assist in analyzing legacy systems, identifying compatibility gaps, and generating structured migration documentation to ensure a smooth transition.

They are designed to reduce manual effort, accelerate planning, and improve accuracy during migration from older Mule versions or other platforms.

Key Benefits:

• Automated Assessment: Quickly analyze existing projects to determine migration feasibility.
• Detailed Documentation: Generate clear, actionable reports outlining what needs to change and how.
• Guided Execution: Identify breaking changes, connector updates, and modernization strategies.
• Cross-Repo Analysis: Support broader architectural review when migrating interconnected services.

Use these agents to accelerate Mule 4 migrations, plan legacy modernization, or scope project complexity with clarity.

1. Migration Generator

Generates detailed migration documents to support the transition to MuleSoft applications from legacy integration platforms — ensuring structured planning and risk mitigation.

• Comprehensive Analysis: Scans your legacy integration project to identify components, endpoints, and triggers that require migration to MuleSoft.

• Platform-Specific Guidance: Tailors recommendations based on the selected source platform. Supported platforms include:

  • TIBCO 5
  • Microsoft BizTalk
  • WebMethods (Cloud & Code Based)
  • IBM App Connect
  • Java Spring Boot
  • Oracle Service Bus
  • TIBCO 6
  • Mulesoft 3

• Input-Flexible Workflow: Works seamlessly whether you connect a Git repository or upload your integration files manually.

Supported Input Modes:

• With Repository: Select a connected git repository containing legacy integration definitions.
• Upload from Computer: Upload exported integration artifacts or local project files.

This agent is ideal for teams preparing assessments, drafting migration plans, or running pilot migrations to MuleSoft from other platforms.

2. Migration Repo Code Lens

Allows you to interactively ask migration-related questions for a specific repository — perfect for getting targeted guidance during the modernization of legacy integrations to MuleSoft.

• Repository-Aware Intelligence: Understands the integration logic in your selected repository and provides migration recommendations accordingly.
• Platform-Specific Migration Help: Choose from platforms like TIBCO 5, WebMethods, IBM App Connect, or Spring Boot to tailor migration answers.
• Interactive Q&A Workflow: Once the repository, branch, and platform are selected, use natural language to ask migration questions.

Supported Input Modes:

• With Repository: Select a git repository and branch to analyze.
• Upload from Computer: (Optional) Import legacy integration files from your local system for migration assistance.

Example Questions You Can Ask:

• "Which SOAP services in this TIBCO 5 project need to be reimplemented for MuleSoft?"
• "What changes are required to migrate JMS listeners from WebMethods to MuleSoft?"

Use this agent during planning or implementation phases to clarify specific migration blockers, understand required transformations, or validate migration approaches.

3. Billable Mule Flows

Analyzes your existing integration project and identifies flows that would be considered billable under MuleSoft 4 — categorized by complexity and based on either direct lift-and-shift or API-led architecture principles.

• Mule 4 Flow Estimation: Calculates the number of Mule flows that would be generated when migrating from a legacy platform like TIBCO 5, BizTalk, WebMethods, etc.
• Two Calculation Modes:
  • Lift and shift: Based on direct conversion of legacy services to Mule 4.
  • API-Led Architecture: Based on MuleSoft’s layered System, Process, and Experience APIs.
• Complexity Rating: Each identified flow includes a Transformation and Orchestration complexity level — e.g., Simple, Medium, Complex.
• Connector Mapping: Maps legacy connectors to their MuleSoft 4 equivalents.
• Interface Inventory: Lists REST endpoints, SOAP operations, and event triggers found in the legacy project.

Supported Input Modes:

• With Repository: Analyze flows directly from a git repository and branch.
• Upload from Computer: Upload your local integration project for evaluation.

This agent is especially useful during the estimation or planning phase of migration, helping teams understand what effort, licensing, and architecture changes are expected when moving to MuleSoft 4.

4. Migration Accelerator

Migration Accelerator is designed for end-to-end migration from legacy platforms to MuleSoft with minimal manual effort. It automates the entire process — from endpoint detection to generating fully runnable MuleSoft code.

• One-Click Full Migration: Automatically detects legacy endpoints, generates API specs, and builds MuleSoft-compatible flows, configurations, and connectors in one seamless workflow.
• Platform Selection Support: Choose from platforms like IBM ACE, Boomi, Tibco 5, Microsoft BizTalk, Oracle Service Bus, and more.
• Endpoint-Based Conversion: You can select specific HTTP, SOAP, or event-triggered endpoints to migrate.

Supported Input Modes:

• With Repository: Connect a branch and select up to 8 repositories containing legacy code.
• Upload from Computer: Upload your zipped project for analysis.

Output Generated After Migration

1. Identified Migration Endpoints: CurieTech AI scans your legacy repository and detects all available service interfaces (e.g., HTTP endpoints, SOAP operations).
2. Endpoint Selection Summary: You select the specific endpoints you wish to migrate, and the chosen ones are marked for conversion.
3. Migration Document: A detailed analysis document is produced, outlining compatibility issues, required changes, and transformation plans.
4. API Specification: An OpenAPI 3.0 specification is generated and transformed into a MuleSoft-compatible API spec.
5. MuleSoft Code Package: Complete Mule 4 implementation is generated — including flows, connectors, and configuration files — ready for deployment.

This is ideal for users seeking to move from legacy platforms to MuleSoft quickly, with well-documented output and minimal manual effort.