Subgraph Migration FAQs

Question 1

What does the Subgraph Migration skill do?

Accepted Answer

This Claude Code skill automates the transition from TheGraph subgraphs to Envio HyperIndex. It intelligently converts configuration files, updates GraphQL schemas to meet Envio's requirements, and refactors AssemblyScript handlers into modern TypeScript async/await logic.

Question 2

What are the main architectural changes it handles?

Accepted Answer

It migrates nested dataSources into Envio's network-first contract structure, ensures all entity arrays use the required @derivedFrom decorator, and switches entity updates to an immutable spread-operator pattern for better reliability.

Question 3

How does this skill improve my developer workflow?

Accepted Answer

It significantly reduces manual refactoring time by handling complex transformations like @derivedFrom schema requirements, Byte-to-String conversions, and the replacement of legacy contract templates with Envio's dynamic contract registration patterns.

Question 4

When should I use this skill?

Accepted Answer

Use this skill whenever you are porting an existing indexer from TheGraph to Envio to achieve better performance. It is ideal for phrases like 'migrate from subgraph', 'convert subgraph handlers', or when moving from AssemblyScript to TypeScript for blockchain indexing.

Question 5

Does it support complex features like RPC calls?

Accepted Answer

Yes. Beyond simple mapping, the skill helps implement RPC calls via the Envio Effect API, replacing legacy contract bindings with high-performance, cached data fetching using viem.

Subgraph Migration

Subgraph Migration

Key Features

Use Cases

Key Features

Use Cases