migrate-to-portal

Migrate Squid v2 indexers from gateway to Portal data sources.

Updated Feb 10, 2026

Search Tags:#migration #portal #data-source #solana #evm #squid #types-and-imports

Ready to run

npx skills add https://github.com/subsquid-labs/skills --skill migrate-to-portal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-to-portal
Source: https://github.com/subsquid-labs/skills/tree/main/squid-sdk/migrate-to-portal
Command: npx skills add https://github.com/subsquid-labs/skills --skill migrate-to-portal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrate an existing Squid SDK indexer from the v2 gateway to the Portal data source, covering package swaps, API shape changes, and field-mapping steps for both EVM and Solana.

Core Features & Use Cases

Guides how to swap packages and update imports for EVM and Solana squids when migrating.
Replaces legacy gateway-based data sources with Portal, and validates Portal dataset mappings.
Helps users migrate, port, upgrade, or debug TS errors like evm- or solana-specific migration issues.

Quick Start

Migrate my Squid v2 indexer to Portal with the new data source and updated imports.

Frequently Asked Questions about migrate-to-portal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate my Squid v2 indexer to the Portal data source?▼

To migrate a Squid v2 indexer to the Portal data source, swap required packages, update imports, replace the legacy setGateway function with setPortal, and harmonize data types and field selections based on migration guidelines.

What is the difference between gateway and Portal data sources in Squid SDK?▼

Portal data sources replace the legacy v2 gateway by introducing new API shapes, updated package imports, and specific field mapping requirements for EVM and Solana indexers to ensure dataset mappings are validated correctly.

Can I use the Portal migration guide for both Solana and EVM squids?▼

Yes, the Portal migration is applicable to both EVM and Solana migrations. It handles platform-specific package swaps, API shape changes, and converts block ranges from height to slot where applicable for Solana indexers.

How do I fix TypeScript errors after updating Squid imports to Portal?▼

Fixing TypeScript errors after updating Squid imports to Portal requires harmonizing data types and adjusting field selections to match the new Portal API shape, ensuring all dataset mappings align with the updated migration guidelines.

Why does my Solana indexer block range need conversion when porting to Portal?▼

When porting a Solana indexer to Portal, block ranges require conversion from height to slot to align with the new data source structure and ensure the indexer queries the correct blockchain data accurately.