Is my Apollo Graph API Key stored?

No. Your API key is used temporarily to fetch the migration data from Apollo GraphOS and is never saved or stored.

What gets imported during the migration?

Cosmo imports your federated graph configuration, including subgraph definitions, schema information, and graph metadata.

Can I migrate multiple variants?

Yes. Run the migration process for each variant by specifying the appropriate variant name. Each variant migrates independently.

Do I need to modify my subgraphs before migrating?

No. The migration imports your existing Apollo configuration. Subgraph code does not need to change.

Can I run Apollo and Cosmo at the same time?

Yes. You can operate both platforms in parallel during your transition period, which lets you validate Cosmo before cutting over production traffic.

What do I need to complete the migration?

You need an active Apollo GraphOS account with configured graphs, a Graph API Key with read permissions, and a Cosmo account. For a full comparison, see Cosmo as an Apollo GraphOS alternative (/use-cases/wundergraph-cosmo-as-apollo-graphos-alternative).

Migrate from Apollo GraphOS to Cosmo in One Click

The problem

Switching platforms without tooling means weeks of manual work

Every subgraph, schema, and routing rule must be recreated from scratch. The effort alone stops most teams from switching.

Manual migration takes days of error-prone work

Re-registering every subgraph, recreating routing rules, and transferring schemas by hand is slow and introduces configuration drift. A single mistake can break the federated graph.

Configuration errors are hard to catch before production

Manual recreation of a complex federated setup leaves gaps. Subtle differences in subgraph configuration often go undetected until a client query fails in a live environment.

Providing credentials to a migration tool raises security concerns

Teams need assurance that their Apollo Graph API Key is handled securely and not persisted anywhere after the migration completes.

Our solution

One click imports your entire Apollo setup

Cosmo's migration tool automates everything. Provide your Graph API Key once. Cosmo fetches the configuration, creates the subgraphs, and imports the schemas. The entire process takes seconds.

How migration works

In Cosmo Studio, click "Migrate from Apollo" on the empty-state screen (visible when your organization has no graphs yet).
Enter your Apollo Graph API Key and the variant name you want to migrate.
Cosmo authenticates and fetches your complete federated graph configuration from Apollo GraphOS.
Subgraphs, schemas, and graph metadata are recreated automatically in your Cosmo organization.
Your API key is used only during this fetch and is never stored.
Your federated graph is live in Cosmo. Run Apollo and Cosmo in parallel during your transition.

One migration. Complete graph. Production-ready from the start.

Apollo GraphOS Migration

Before & After

Before Cosmo	With Cosmo
Days of manual subgraph registration	One-click automated import in seconds
Risk of configuration errors during recreation	Accurate replication of the existing Apollo setup
Downtime risk during the transition	Parallel operation possible throughout migration
Manual schema transfer across environments	Automatic schema import for each variant

Security

Your API key is never stored

Temporary use only: The Graph API Key is used once to fetch your Apollo configuration. It is never persisted in Cosmo's systems.
Read-only access: The migration only reads your graph configuration from Apollo. No changes are made to your Apollo account.

How Apollo GraphOS migration works

01

Takes seconds.

Enter

In Cosmo Studio, click "Migrate from Apollo" on the empty-state screen (shown when your organization has no graphs yet). A modal appears requesting your Graph API Key and Graph Variant Name.

02

Key never stored.

Fetch

Cosmo authenticates with Apollo GraphOS using your API key and fetches the complete federated graph configuration. The key is used only for this request and is never stored.

03

Complete configuration.

Recreate

Cosmo recreates your federated graph in your organization: subgraph definitions, schema configuration, and graph metadata are all imported automatically.

04

Parallel operation supported.

Run

Your federated graph is live in Cosmo. You can run Apollo GraphOS and Cosmo in parallel during the transition, then cut over at a time of your choosing.

What's included

Everything you need to migrate

Available on Free, Pro, and Enterprise. No extra configuration required.

One-click import

The entire migration — subgraph registration, schema import, graph configuration — completes automatically from a single modal in Cosmo Studio.

API key never stored

Your Graph API Key is used once to fetch the migration data and is never persisted. The process is secure by design.

Complete configuration import

Subgraph definitions, schema information, and graph metadata are all imported. No manual recreation of any part of your federated setup.

Parallel operation

Run Apollo GraphOS and Cosmo simultaneously during your transition. Cut over production traffic when you are ready, with no pressure to decommission Apollo immediately.

Migrate your Apollo graph today

Sign up for Cosmo and click "Migrate from Apollo" in the Studio. The process takes seconds.

Start Free Read the Docs

Import your Apollo GraphOS setup with a single click