Migrating from Apigee to Tyk can deliver the lightweight, highly performant and ultra-flexible API management solution you deserve. Cost-effective even for the most complex use cases, Tyk provides plenty of reasons to say goodbye to Apigee.
Ready for a highly customizable solution that empowers you to achieve more with your APIs, whether you’re using REST, GraphQL, gRPC or async APIs? Then here’s how to migrate from Apigee to Tyk.
Migrating from Apigee to Tyk
If you’re ready to migrate away from Apigee, this guide will walk you through everything you need to know. We’ll be using the Google Cloud console for Apigee, manually copying and pasting data from the Apigee user interface to Tyk Dashboard. We’ve covered simple configuration below, so you can get the API up and running in Tyk quickly and easily.
Note that our Apigee migration guide uses the Google Cloud-hosted Apigee, known as Apigee X. We’ve used Apigee version 1-14-0-apigee-7 and Tyk Dashboard 5.7.1 to walk you through the process of migrating to Tyk.
How to migrate from Apigee to Tyk: a GUI-based approach
Start the migration by opening the API Proxies section in Apigee and navigating to the API proxy page for the API you want to export. There, click on the Develop tab and then on Display Name in the Proxy Revision section.
If nothing is showing in the Display Name field, you can copy the API’s name from the top of the Proxy Revision section instead.
Now paste the API name into the API Definition Name field in Tyk.
Next, while still in the Develop tab in Apigee, expand the Proxy Endpoints section. Select the proxy endpoint and copy the value of the BasePath field from the XML document part of the page.
Paste this into the Listen Path field in Tyk.
Don’t worry if multiple proxy endpoints are defined. You can easily migrate these by combining all the paths into a single regular expression. Let’s say, for example, you have three Apigee proxy endpoints: /apple, /banana and /cherry. You can migrate these to Tyk as a single listen path: /{path:apple|banana|cherry}/.
Next, still in the Develop tab, expand the Target Endpoints section. Select the target endpoint and copy the value of the URL field from the XML document part of the page.
Paste this value into the Target URL field in Tyk. If you have multiple target endpoints defined in Apigee, you can set them up in Tyk by checking the “enable round-robin load balancing” option. You can then add each as a separate target URL.
Now it’s time to check your work. The API definition in Tyk should now contain all the details of the API you’re migrating: API name, listen path (API URL) and upstream target URL.
Save the API and your work is done – you’ve successfully migrated the API from Apigee to Tyk. It will now be accessible through Tyk Gateway.
Start delivering exceptional API experiences
Using Tyk to manage your API ecosystem empowers you to deliver exceptional API experiences. We put outstanding flexibility and customizability at your fingertips, all without locking you into any specific vendors or tools. You can do things your way, with robust security, seamless governance and efficient automation helping you reach your goals faster while enjoying exceptional peace of mind.
Why not speak to our expert team to find out more about the benefits of Tyk and how to migrate from Apigee?
