Loading
Salesforce Enforces New Security Requirements in Summer 2026Read More

How to Migrate Your Projects from Anypoint Code Builder Cloud IDE to the Desktop IDE

Publish Date: Aug 4, 2026
Description

Anypoint Code Builder (ACB) is available as a browser-based Cloud IDE (Web IDE) and as a Desktop IDE delivered through the Anypoint Extension Pack for VS Code. The Cloud IDE was released as a Beta to enable browser-based Mule development without a local setup, but adoption has remained low as most developers prefer working in their own local environment. Recent trends in AI adoption and use of Developer Agents to build Mule Applications, with "MuleSoft, your way," customers can install the Anypoint Extension Pack in any VS Code–based AI IDE — such as Cursor or Windsurf, or via the Skills CLI in Claude Code — and continue developing in their preferred environment. Given this flexibility and the low adoption of the Cloud IDE, the ACB Cloud IDE is being retired on August 15, 2026, after which projects on a decommissioned instance cannot be recovered.

After the retirement date, projects stored in the Cloud IDE will no longer be accessible, and instances will be decommissioned without backup. To avoid losing work, you must export each of your projects and continue your development in the ACB Desktop IDE, which is supported on both Windows and macOS and offers a richer development experience.

Resolution

Before you begin:

  • Install the ACB Desktop IDE for your operating system (Windows or macOS) following the instructions from the documentation.
  • Make sure you have access to your Cloud IDE workspace with all projects you intend to migrate.
  • Complete this migration before the announced retirement date — instances cannot be restored once removed.

Choose one of the following methods for each project:

Option A — Download the project from the Cloud IDE

Use this method if your project is not tracked in a Git repository, or you simply want a local copy of the files.

  • Open the project in the ACB Cloud IDE (US or EU).
  • In the Explorer panel, right-click the project's root folder.
  • Select Download. Your browser will download the project as a compressed archive (.zip).
  • Alternatively: right-click the project folder, choose the Mule menu, then select Export Project. This opens the export dialog (shown below), which produces a packaged .jar file of the project.


In the export dialog:

  • File Name — enter a name for the exported file (e.g. Global_elements_tst2).
  • File Location — click Browse to choose where the .jar will be saved.
  • Select an Export Type:
    • Deployable JAR — packages the project for deployment to the Mule runtime.
    • Shareable JAR — packages a lightweight version of the project for sharing.
  • Include Project Sources — leave this checked to bundle the project source files so the project can be reopened and edited in the Desktop IDE.


image.png

  • On your local machine, extract the downloaded file (.zip from Download, or .jar from Export) to the folder where you keep your projects.
  • Open the ACB Desktop IDE.
  • Select File → Open Folder and choose the extracted project folder.
  • Wait for the Mule extension to load and resolve dependencies. Your project is now ready for development on the Desktop IDE.

Option B — Migrate using Git

Use this method if your project is already connected to a Git repository (GitHub, GitLab, Bitbucket, etc.). This preserves your full commit history.

  1. In the ACB Cloud IDE, open the project and confirm all your latest changes are committed and pushed to the remote repository:
    1. Open the Source Control panel.
    2. Stage any pending changes, enter a commit message, and Commit.
    3. Click Sync / Push to push commits to the remote.
  2. Copy the repository's clone URL from your Git provider.
  3. Open the ACB Desktop IDE.
  4. Open the Command Palette (Ctrl+Shift+P on Windows, Cmd+Shift+P on macOS) and run Git: Clone.
    1. Alternatively: select Clone Repository from the Welcome screen.
  5. Paste the clone URL and choose a local folder to store the project.
  6. When prompted, select Open to open the cloned project.
  7. Wait for the Mule extension to load and resolve dependencies. Your project, including its full history, is now available on the Desktop IDE.

Verify the migration

After opening the project in the Desktop IDE:

  • Confirm the project structure (src/main/mule, pom.xml, configuration files) appears in the Explorer.
  • Open a Mule configuration file and confirm the flow canvas renders.
  • Run or deploy the project to confirm it builds successfully.
Additional Resources
  • The ACB Desktop IDE supports secure local development, offline access, and integration with enterprise CI/CD pipelines.
  • Because ACB is delivered as a VS Code extension, you can also install the Anypoint Extension Pack in any VS Code-based AI IDE — such as Cursor or Windsurf — and follow the same migration steps above.
  • If you have a business-critical reason that prevents migration before the retirement date, Contact your Account Representative or the MuleSoft Saales team.
Knowledge Article Number

005390309

 
Loading
Salesforce Help | Article