# Contract Migration

In some cases, for example when wanting to deliver support to users and deploy bug fixes, it makes sense to have the ability to change the code. This is especially true for services which wish to change algorithms, add features, etc. For these use cases, contracts can be written to allow various modes of migration. Doing so means that anyone inspecting the source code will be able to *know* that such a migration is possible and will require that users have a higher level of trust in the contract administrators, as they can effectively install a backdoor in their product.

**Secret used to not support the native CosmWasm implementation of contract migratability, since v1.11 it does.**\
\
The old manual examples are still displayed here as a reference.<br>

{% hint style="info" %}
During the v1.11 upgrade a set of old contracts were allowed to become migrateable, these contracts behave slightly different in that they are callable by both their new and old code hash.\
\
**For more information about the transition period** please read [this forum post!](https://forum.scrt.network/t/an-update-on-the-contract-upgrade-feature/7012)
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.scrt.network/secret-network-documentation/development/development-concepts/contract-migration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.