+

Migration to Mule 4

Standard Support for Mule 4.2 ended on May 2, 2021, and this version of Mule will reach its End of Life on May 2, 2023, when Extended Support ends.

Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted.

MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements.

For your Mule 3 apps to take advantage of Mule 4, migrate them to Mule 4 through one of the following processes:

  • A fully manual migration of connectors, modules, transports, expressions, and API gateways to their Mule 4 counterparts.

    For guidance with a fully manual migration, see Prepare to Migrate and review Manual Migration Process.

  • A partially automated migration with the Mule Migration Assistant (MMA), which is available as an open source project on GitHub.

    For guidance using MMA to assist in a migration, see the user documentation (on GitHub). MuleSoft suggests that you try MMA to determine whether you prefer it to a fully manual migration. Note that you can run MMA on a sample application by following steps in the Migration Tutorial (on GitHub).

Important

Mule Migration Assistant (MMA) is subject to the terms and conditions described for Community connectors. Additionally, Mule Migration Assistant is distributed under the terms of the 3-Clause BSD License.

A benefit of using MMA is that it automates part of the migration of Mule 3 apps to Mule 4. Though the MMA does not migrate the app entirely, it provides significant help with the following tasks:

  • Migrating the project structure.

  • Automatically creating descriptor files, such as pom.xml or mule-artifact.json.

  • Automatically performing many adaptations of the app’s code.

  • Providing guidance on how to manually migrate components and patterns that cannot be migrated automatically.

MMA helps with such tasks, but it does not deliver a fully functional app. Some additional steps are required. Those steps include testing and can also include:

  • Manual migration of unsupported components.

  • Manual migration of complex MEL expressions to DataWeave that cannot be automatically converted by MMA.

  • Manual migration of complex DataWeave transformations that cannot be automatically converted by MMA.

  • Prior migration of the DataMapper with the DataWeave Migration tool, before running the MMA.

It is also important to note that the MMA does not support incremental migrations.

Was this article helpful? Thanks for your feedback!
View on GitHub