How to migrate your subgraph in 3 minutes

​

Before you start

There are important differences between providers. Not all subgraph hosting services follow the same conventions.
Because of this, one-click migration may fail in certain cases. Here are the two main things to check:

​

#1. Different IPFS gateways

Some providers use private IPFS nodes instead of the default public gateway. For example: If a subgraph was originally deployed using a private IPFS gateway, the metadata cannot be fetched from the default public gateway. This prevents one-click migration from pulling the manifest and files.

​

Solution

Use the Custom IPFS Gateway field in the migration form, and enter the gateway used by the previous provider.

​

#2. Different network naming conventions

Subgraph hosting platforms sometimes label the same chain differently: If the chain name in the original deployment does not match Ormi’s naming, the one-click migration will not know which chain to sync against.

​

Solution

First, confirm the naming convention on Ormi. You can see the network slug in the one-click migration feature under Identify the network you want to deploy to or in our Supported Chains page. Afterwards, you will have to manually deploy using the CLI and update the network name in subgraph.yaml to match Ormi’s expected chain ID. We recommend this if your migration errors mention:

• invalid network
• mismatch in chain ID
• unsupported network name

To manually deploy via CLI, please check out our Deploy subgraphs via CLI guide.

​

Getting started

1. In the Ormi dashboard, click 0xGraph
2. Expand the Migrate from another provider section

Note: If you already deployed a subgraph, click on Deploy Subgraph for the window to pop up. Keep this tab open. We’ll come back to this part in a moment.

​

How to find the deployment ID using The Graph Explorer

​

Find the subgraph you want to migrate and copy the deployment ID

In this guide, we’ll be migrating Uniswap v4 on Base Chain from TheGraph.

​

Head back to the 0xGraph page

Complete the required fields in the Migrate from another provider section

1. Deployment ID: QQmS1ehFzXTD9eA1f1EgjZvdyAj2EHtVNMrEN91H3pLuHMy
2. Network: Base
3. Name: base-uniswap-v4
4. Version: v.1

After entering these details, you’ll be redirected to the 0xGraph dashboard, where your subgraph will start syncing automatically. That’s it! Once your subgraph syncs, you’ll be able to query data directly through Ormi’s 0xGraph.

​

If migration fails

If you run into errors during migration, it is usually caused by either:

• A private IPFS gateway used by the original provider
• A network naming mismatch

In these cases, follow our manual deployment guide: -> Deploy via CLI instead

​

How to access your Subgraph endpoint

​

Step #1: Click on the >_ icon

​

Next steps

1. Click on API Endpoint
2. Press Rest API
3. Copy URL