---
schema_version: "1"
id: 6e11aba2d62dc86fd66db14d3b55297d0af6382acfa1a7cffcee1844f0cf807a
title: Migrating Assets from Exchange 1
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/exchange/migrate.md
canonical_url: https://docs.mulesoft.com/exchange/migrate
source_site: docs.mulesoft.com
content_type: documentation
content_hash: bfbf7f60ca44ab3e303582dc377e7df58989b00c216fc587a61e34e1f807ad53
description: MuleSoft Documentation Site
latest: true
---
---
product: Exchange
---

# Migrating Assets from Exchange 1

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

> [!NOTE] The end of life date for Exchange 1 is July 18, 2021.

Anypoint Exchange 2 introduces a new way of working with your assets. Where Exchange 1 is a listing
service that only provides links to where assets are stored, Exchange 2 is a package management
system that stores assets.

Migration to Exchange 2 differs by asset type:

<table><colgroup><col> <col></colgroup><thead><tr><th>Asset Type</th><th>Migration Approach</th></tr></thead><tbody><tr><td><div><div><p>Example, Template</p></div></div></td><td><div><div><p>Maven - see <a href="https://docs.mulesoft.com/exchange/to-publish-assets-maven">Publish and Deploy Exchange Assets Using Maven</a></p></div></div></td></tr><tr><td><div><div><p>OAS REST API</p></div></div></td><td><div><div><p>Publish using Exchange.</p></div></div></td></tr><tr><td><div><div><p>RAML REST API</p></div></div></td><td><div><div><p>Publish using API Designer or Exchange.</p></div></div></td></tr><tr><td><div><div><p>WSDL SOAP API</p></div></div></td><td><div><div><p>Publish using Exchange.</p></div></div></td></tr><tr><td><div><div><p>Connectors</p></div></div></td><td><div><div><p>Use Node.js connector-uploader program.</p></div></div></td></tr></tbody></table>

## Migrate an Example or Template to Exchange

Note: This procedure requires Maven.

1.  In Anypoint Exchange 1, for an example or template from your private Exchange, click Download to
    copy the asset to your computer.

2.  Open Anypoint Studio 6.4.1 and later, and click File > Import.

3.  In the Import menu, click Anypoint Studio > Anypoint Studio Generated Deployable Archive (.zip).
    Click Next. For the zip file name, click the `…​` browse button, click the name of the zip file
    you downloaded, and click Open.

4.  Click Finish. Click OK for the Runtime version.

5.  If you have not used Maven before, right-click the project name in the Package Explorer and
    click Mule > Configure Maven to locate the folder where you downloaded Maven. In Studio, click
    Test Maven Configuration to ensure Maven is ready to use and click OK.

    When Maven is ready, right-click the project name in the Package Explorer and click Mule >
    Mavenize. At the Maven Support prompt, click Yes.

6.  In the Action to Perform menu, click OK.

7.  Right-click the project name and click Anypoint Platform > Publish to Exchange.

8.  Studio prompts you for your Anypoint Platform username and password. Click Signin. Or click
    Configure to specify an external identity provider such as OAuth and the organization’s domain.

9.  In the Publish to Exchange menu:

    1.  If present in the Name field, remove special characters such as an underscore and
        parentheses. Only letters, numbers, spaces, dots, and dashes are permitted.

    2.  If present in the Version field, remove the `-SNAPSHOT` value.

    3.  Set the Project Type to either Example or Template as needed.

10. After setting all fields as required, click Finish. Click Yes for the Proceed Anyway prompt.

11. Upon successful deployment, a link appears to let you view the asset in Exchange 2. Click the
    link.

12. Click the asset in Exchange 2 and click Edit. In the Exchange editor, click Visual. Copy the
    description text from Exchange 1 to the Exchange 2 editor and paste the description into the
    editor. Format as needed. Click Save As Draft to save your edits. Click Publish.

13. In Studio, click OK to dismiss the publish to Exchange menu.

## Migrate a SOAP API WSDL

1.  Go to Exchange 1 and download your WSDL file.

2.  Go to Exchange 2 and click New.

3.  Select API Spec - WSDL in the types drop-down.

4.  In the File field, select your WSDL file.

5.  Fill in the remaining fields.

6.  Click Create.

## Migrate a REST API RAML

_Requires November 2017 Release_

1.  Go to the API Manager Portal for the API and export the API Specification as a zip file.

2.  Go to Design Center API Designer and create a project of type API Specification.

3.  Import the zip.

4.  Publish to Exchange 2.

## Migrate Connectors From Exchange 1 to Exchange 2

1.  Download and install NPM.

2.  Log into your private Exchange and download the connector to your computer.

3.  Locate the connector’s JAR file, pom.xml file, and Studio Plugin zip file.

4.  Get the connector-uploader Node.js application:

    npm install -g connector-uploader

5.  Run the upload program:

    connector-uploader

6.  When prompted, enter the Anypoint Platform credentials for the organization you want to upload
    the connector to. You are asked to select a business group and enter the Asset ID and version.
    The Group ID is generated for you. You are prompted to specify each file to upload if you are
    uploading more than one connector.

## See Also

- [Migrate SOAP Assets Video](https://www.youtube.com/watch?v=BOAR9glreMw&feature=youtu.be)

- [Migrate RAML REST Assets](https://www.youtube.com/watch?v=WTIJrYydViQ&feature=youtu.be)