Guide: Migrate an Existing dApp's RPC Endpoint

1. Identify every place your codebase references your current RPC provider's URL: environment variables, config files, and hardcoded fallback URLs.
2. Deploy the equivalent chain and node type on Instanodes (see Deploy your first node).
3. Update your environment configuration to point at the new endpoint. Use a feature flag or environment-specific override, so you switch back quickly if needed.
4. Run your existing integration and test suite against the new endpoint. Instanodes speaks standard JSON-RPC, so this step requires no code changes, only configuration changes.
5. Shadow-test in production: send a percentage of read traffic to the new endpoint while keeping your old provider live, and compare latency and error rates before cutting over fully.
6. Once you're confident, switch 100% of traffic and keep the old provider's credentials active for a short rollback window before decommissioning them.

If you move from Alchemy, Infura, or QuickNode specifically, the request format does not change at all. Only the endpoint URL changes. See Get Started for the standard request pattern.