---
schema_version: "1"
id: fe690ae831c727109163e4de54127d667f890998e90e7b26def35b3e1e16b204
title: Migrating Mule Projects from Anypoint Studio to Anypoint Code Builder
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/int-migrate-studio-to-acb.md
canonical_url: https://docs.mulesoft.com/anypoint-code-builder/int-migrate-studio-to-acb
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 9caab89edbb103d920ec9e4fac6cb76a7a5b74c4b16c624e5b826ecc522346ca
description: MuleSoft Documentation Site
latest: true
---
---
product: Anypoint Code Builder
version: master
---

# Migrating Mule Projects from Anypoint Studio to Anypoint Code Builder

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

Migrate your Mule projects from Anypoint Studio to Anypoint Code Builder to unlock a modern
development experience with advantages like faster startup times, streamlined collaboration, and the
integration of MuleSoft for Agentforce: Topic Center to enable API specifications for topics and
agents.

## Choose a Migration Approach

Anypoint Code Builder provides three ways to bring your Studio projects over.

<table><colgroup><col> <col></colgroup><thead><tr><th>Approach</th><th>When to Use It</th></tr></thead><tbody><tr><td><div><div><p>Import a Studio workspace</p></div></div></td><td><div><div><p>Bring over an existing Studio workspace and keep working against the same project files. Anypoint Code Builder creates a workspace that references your Studio projects, and changes stay in sync. See <a href="https://docs.mulesoft.com/anypoint-code-builder/start-workspaces#import-studio-workspace">Import an Anypoint Studio Workspace</a>.</p></div></div></td></tr><tr><td><div><div><p>Export and import a JAR file</p></div></div></td><td><div><div><p>Package a single Mule project as a sharable JAR file in Studio and import it into Anypoint Code Builder by following the steps on this page.</p></div></div></td></tr><tr><td><div><div><p>Open the project folder directly</p></div></div></td><td><div><div><p>Open an existing Studio project folder in Anypoint Code Builder without packaging it, which is the fastest path when the project is already on your machine. See <a href="https://docs.mulesoft.com/anypoint-code-builder/int-import-mule-project">Importing Projects into Anypoint Code Builder</a>.</p></div></div></td></tr></tbody></table>

## Set Run and Debug Configurations

In Anypoint Studio, you configure run and debug settings through the UI with tabs for arguments,
environment, and other settings. In Anypoint Code Builder, you manage these configurations by
editing the `launch.json` file in your project’s `.vscode` folder.

<table><colgroup><col> <col></colgroup><thead><tr><th>Studio UI</th><th>Anypoint Code Builder</th></tr></thead><tbody><tr><td><div><div><p><strong>Run Configurations</strong> &gt; <strong>Arguments</strong> tab &gt; <strong>VM arguments</strong></p></div></div></td><td><div><div><p><code>mule.runtime.args</code> property in launch.json</p></div></div></td></tr><tr><td><div><div><p><strong>Run Configurations</strong> &gt; <strong>Environment</strong> tab</p></div></div></td><td><div><div><p>Environment variables passed via <code>mule.runtime.args</code> (e.g., <code>-M-Denv=dev</code>)</p></div></div></td></tr><tr><td><div><div><p><strong>Run Configurations</strong> &gt; <strong>Port</strong> settings (if available)</p></div></div></td><td><div><div><p><code>mule.debug.port</code> property in launch.json</p></div></div></td></tr><tr><td><div><div><p>Configuration dropdown in toolbar</p></div></div></td><td><div><div><p>Configuration dropdown in <strong>Run and Debug</strong> view</p></div></div></td></tr></tbody></table>

For a reference of `launch.json` properties, see
[Launch Configuration Properties Reference](https://docs.mulesoft.com/anypoint-code-builder/ref-launch-json-properties).

## Export Your Mule Project to a Sharable JAR File in Anypoint Studio

1.  Open the project to export in Anypoint Studio.

2.  Select **Export** from the **File** menu.

3.  Click to expand the Mule folder.

4.  Select **Anypoint Studio Project to Mule Deployable Archive (includes Studio metadata)** and
    click **Next**.

5.  Select the project to export and click **Next**.

6.  In the **JAR file** menu, click the ellipses (…​) button to explore your local drive, and select
    the folder to which you want to export your deployable JAR file.

7.  Click **Finish**.

### Exporting Considerations

- Select **Attach Project Sources** to include the project metadata if you plan to:

  - Reimport the deployable file as an open Mule project into your workspace

  - Import the JAR file into Anypoint Code Builder

  - Import the JAR file back into the same Studio workspace

> [!NOTE] Selecting **Attach Project Sources** flags the `-DattachMuleSources` parameter as if you
> would pack your Mule project with Mule Maven Plugin.

- Select **Include project module and dependencies** if you plan to deploy your exported Mule
  project to CloudHub.

## Import a Mule Project from a Sharable JAR File in Anypoint Code Builder

Import a shareable JAR file for a snapshot of a Mule project into Anypoint Code Builder.

To create a shareable JAR, see [Export Mule Project](https://docs.mulesoft.com/anypoint-code-builder/int-export-mule-project#export-mule-project).

To import a shareable JAR file into Anypoint Code Builder:

1.  Make sure that no project is open.

2.  Open the Command Palette.

    Show me how

    - Use the keyboard shortcuts:

      - Mac: Cmd+Shift+p

      - Windows: Ctrl+Shift+p

    - Select **View** > **Command Palette**.

3.  Provide the following command:

    ```command
    MuleSoft: Import a Mule Project
    ```

4.  Navigate to the shareable JAR file to import, and click **Select jar file to import**.

5.  Navigate to a folder to which to unpack the JAR file, such as your home directory or any folder
    _outside_ of a Mule project folder.

6.  Click **Select project folder**.

    Anypoint Code Builder unpacks the shareable JAR file for your project into the selected folder.

7.  If your Mule project folder is closed,
    [open a workspace](https://docs.mulesoft.com/anypoint-code-builder/int-import-mule-project#both-open-project-folder) for the project at the
    project’s _root_ directory.

    In addition to loading the graphical canvas, Anypoint Code Builder also loads dependencies
    defined in the `pom.xml` for the project. If a Mule runtime or Java configuration is missing,
    set the versions to use from the canvas.

    Libraries load to the `target/repositories` directory within the project folder.

8.  Test your project:

    1.  In the open project, check for errors and make sure that the canvas and code editor load
        correctly, which indicates that component dependencies resolved.

    2.  Check for any configurations to modify, such as ports or file paths in the configuration
        XML.

    3.  Run and debug your project:

        For guidance, see [Run Your Application in Debug Mode](https://docs.mulesoft.com/anypoint-code-builder/int-debug-mule-apps#run-debug-mode).

## Set Up Your Development Environment

After your project is in Anypoint Code Builder, set up your development environment:

- Organize your projects in a workspace so that all Anypoint Code Builder features work correctly.
  See [Working with Workspaces](https://docs.mulesoft.com/anypoint-code-builder/start-workspaces).

- Manage the folders that store your projects. See
  [Adding Folders to Your Home Directory](https://docs.mulesoft.com/anypoint-code-builder/start-add-folders).

- Connect your project to a Git repository for source control. See
  [Controlling Source Files](https://docs.mulesoft.com/anypoint-code-builder/start-scm).

You don’t need to restructure a migrated project all at the same time. Confirm that the project
opens and runs first, then adopt Anypoint Code Builder conventions over time, for example, by
centralizing global elements that are scattered across flow files into `global-config.xml`, moving
from `.properties` files to environment-specific property files such as `config-dev.yaml` and
`config-prod.yaml`, and introducing MuleSoft Vibes for new work while leaving existing flows as they
are.

If multiple developers work on the same set of projects, migrate one project at a time rather than
switching everyone over at the same time. Anypoint Studio and Anypoint Code Builder both produce
standard Mule artifacts, so you can run them side by side during the transition without affecting
CI/CD pipelines, deployments, or runtime behavior.

## See Also

- [Importing Projects into Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/int-import-mule-project)

- [Launch Configuration Properties Reference](https://docs.mulesoft.com/anypoint-code-builder/ref-launch-json-properties)