---
schema_version: "1"
id: 5edc4c9789a64cb5021170816550c2d50f33dd1ed5825f309f7d24cba3d64417
title: Prepare to Migrate to Mule 4
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.4/migration-prep.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.4/migration-prep
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 184a5d224852a790990f39dba107bbafd434bdd138cedcaed6a07ca23016c360
description: MuleSoft Documentation Site
release: "4.4"
latest: false
---
---
product: Mule Runtime
version: 4.4
---

# Prepare to Migrate to Mule 4

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Mule 4 introduces many changes, so plan accordingly before attempting to migrate from Mule 3.

## When to Start Using Mule 4

MuleSoft recommends that you develop all **new** projects on Mule 4, provided that:

- You and your team have updated your skills for Mule 4 through the documentation or formal
  training.

- You have the [proper deployment environment](#prepare_dev_environ).

For projects deployed on Mule 3, use the Mule Migration Assistant (MMA) to avoid re-creating the
application in Mule 4.

Migrate your applications if any one of the following conditions is met:

- The 3.x version you are using reaches end of life.

- You want to make significant updates to the existing applications.

- You want to take advantage of key Mule 4 capabilities.

- You decide to upgrade all your apps to Mule 4 because your organization requires all apps to be on
  one version (for some on-prem scenarios).

## Setting up Your Local Development Environment

First, download and install Anypoint Studio 7. If the Mule version that comes with Anypoint Studio
does not match the Mule version you want to use for local deployments, download the desired 4.x
version of Mule runtime engine.

## Getting Ready to Deploy

Next, you need to make sure your deployment environment is ready. Depending on which environment you
have, different steps may be required.

<table><colgroup><col> <col></colgroup><thead><tr><th>Deployment Mechanism</th><th>Instructions</th></tr></thead><tbody><tr><td><p>CloudHub</p></td><td><p>CloudHub is Mule 4 ready.</p></td></tr><tr><td><p>Hybrid Deployment</p></td><td><p>Install Mule 4 on your servers.</p></td></tr><tr><td><p>Anypoint Runtime Fabric</p></td><td><p>Runtime Fabric supports Mule 4.</p></td></tr><tr><td><p>Anypoint Platform Private Cloud Edition (PCE)</p></td><td><p>PCE supports Mule 4.</p></td></tr></tbody></table>

## Writing the Code

If you are performing a completely manual migration, you are ready to start building and deploying
Mule 4 applications. Simply review [Introduction to Mule 4](https://docs.mulesoft.com/mule-runtime/4.4/intro-overview) topics to get an
overview of the migration process and understand changes introduced in Mule 4.

For guidance with an assisted migration using the Mule Migration Assistant (MMA), it is important to
review the
[MMA documentation (on GitHub)](https://github.com/mulesoft/mule-migration-assistant/blob/master/docs/migration-intro.adoc#migration_process).

Important

**Mule Migration Assistant (MMA) is subject to the terms and conditions described for
[Community](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf)
connectors. Additionally, Mule Migration Assistant is distributed under the terms of the
[3-Clause BSD License](https://github.com/mulesoft/mule-migration-assistant/blob/master/LICENSE.txt).**