Migrating data from an Apigee Evaluation org

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info

You can migrate code in your Apigee Edge organization from one Evaluation organization to another, or from an Evaluation organization to a paid plan organization. Using the Apigee migrate tool, you can migrate most of the code, leaving just a few pieces to copy over manually.

The Apigee migrate tool is an open source tool that uses a JavaScript task runner, Grunt. The tool makes calls to Apigee management APIs for both the orgs you're working with.

You'll find the tool in the migrate tool GitHub repository.

Data migrated

With the tool, you can import and export data about:

• developers
• proxies (latest version)
• shared flows
• products
• apps
• app keys
• KVMs (org and env)

You can also import the following kinds of data from a CSV file to an Apigee org:

• developers
• apps
• app keys
• KVMs (org and env)

Data not migrated

Please note that the following entities won't be migrated as part of this tool. In most cases, you'll need to migrate these manually using the Apigee Edge console.

• Cache resources and cached values. Please recreate the cache resources before deploying your proxies.
  • For more, see Creating and editing an environment cache.
• Environment resources such as target servers, virtualhosts, and keystores. For more information, see:
  • Load balancing across backend servers
  • About virtual hosts (Beta)
  • Keystores and Truststores
• KVM entries for "encrypted" key-value maps. Encrypted values can't be retrieved using the management API. Make a note of the values you're using in your old org, then add these values manually to the new org.
  • See Working with key value maps.
• Organization or environment level resources such as .jar files, .js files, and so on.
• Analytics data. This data can't be migrated.
• Flow hooks. You can use the UI to download these and import them into the new org.
  • For more, see Attaching a shared flow using a flow hook.

Using the Apigee migrate tool

The Apigee migrate tool is an open source Node.js tool that uses the task runner, Grunt. Once you download the tool, you configure it with information about your old and new orgs. Then you run migrate tool tasks to export and import the parts of your org.

At a high level, migration includes the following steps:

1. Collect information about the orgs you're migrating from and importing to. For example, you'll need:
   • Base URL for management API calls, such as https://api.enterprise.apigee.com
   • An org admin's user ID and password. For example, these are the credentials used to log in to the Apigee Edge management console.
   • The old org's name and environment.
   • The name of the target org environment to which the migrated pieces are deployed.
2. Configure the tool with information about your orgs.
3. Run Grunt tasks defined in the migration tool to export org data to your local drive, then import the data to another org.
4. Verify that the data you migrated works as it should in the new org.

To get started with migration, use documentation in the migration tool repository to install, configure, and run the tool.