Migrate from The Graph or another host
Goldsky provides a one-step migration for your subgraphs on The Graph’s hosted service / decentralized network, or other subgraph host (including your own graph-node). This is a drop-in replacement with the following benefits:
- The same subgraph API that your apps already use, allowing for seamless, zero-downtime migration
- A load-balanced network of third-party and on-prem RPC nodes to improve performance and reliability
- Tagging and versioning to hotswap subgraphs, allowing for seamless updates on your frontend
- Alerts and auto-recovery in case of subgraph data consistency issues due to corruption from re-orgs or other issues
- A world-class team who monitors your subgraphs 24/7, with on-call engineering support to help troubleshoot any issues
Migrate subgraphs to Goldsky
Install Goldsky's CLI and log in
Install Goldsky's CLI and log in
-
Install the Goldsky CLI:
For macOS/Linux:
For Windows:
Windows users need to have Node.js and npm installed first. Download from nodejs.org if not already installed. -
Go to your Project Settings page and create an API key.
-
Back in your Goldsky CLI, log into your Project by running the command
goldsky login
and paste your API key. -
Now that you are logged in, run
goldsky
to get started:
If you have subgraphs deployed to The Graph’s hosted service, the following command seamlessly migrates your subgraph to Goldsky:
If you have subgraphs deployed to The Graph’s decentralized network, use the IPFS hash instead (visible on The Graph’s Explorer page for the specified subgraph):
You can get this IPFS deployment hash by querying any subgraph GraphQL endpoint with the following query:
Monitor indexing progress
Once you started the migration with the above command, you can monitor your subgraph’s indexing status with:
Alternatively, navigate to app.goldsky.com to see your subgraphs, their indexing progress, and more.