> For the complete documentation index, see [llms.txt](https://docs.cogitus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogitus.io/faqs/migration-and-upgrades.md).

# Migration & Upgrades

<details>

<summary><strong>Can I migrate my existing blockchain to an Avalanche L1 with Cogitus?</strong></summary>

Yes, Cogitus provides complete support for migrating any EVM-based or custom chain to
&#x20;Avalanche L1.

</details>

<details>

<summary><strong>What kind of networks can be migrated (L1, L2, L3)?</strong></summary>

You can migrate L1, L2, or L3 chains to Avalanche with data continuity, validator
\
reconfiguration, and ecosystem adaptation.

</details>

<details>

<summary><strong>How does Cogitus handle state and data migration?</strong></summary>

Cogitus performs a full export/import of on-chain data, redeploys contracts, and maps
&#x20;token balances during migration.

</details>

<details>

<summary><strong>Will I lose any token balances, user data, or smart contracts during migration?</strong></summary>

No, Cogitus ensures full data continuity with pre-migration snapshots and validation to
&#x20;prevent data or token loss.

</details>

<details>

<summary><strong>Can I upgrade my Avalanche L1 chain after launch? How are upgrades managed?</strong></summary>

Yes, Avalanche L1 chains can be upgraded via the dashboard or CLI with minimal
\
downtime and audit logging.

</details>

<details>

<summary><strong>What support is provided during and after migration?</strong></summary>

Full support includes pre-migration consultation, technical validation, post-migration
\
monitoring, and ongoing maintenance.

</details>