# Migrate

![](/files/-M71kBoa3XXERKyb0tkX)

*Figure 14: Migrate (Admin side)*

For developers of the module, we provide a "Migration" option

![](/files/-M71kBobqzeRNiandtr8)

*Figure 15: View SQL differences(Admin side)*

If the module database schema is in synch with the database, then there are no SQL commands here. However, since we just changed the version number of the module, there is no schema yet, therefore the "Show SQL" button shows all the code

![](/files/-M71kBoc5_8SzfNxZ2Le)

*Figure 16: Writing the schema (Admin side)*

When you make changes to the ModuleBuilder database structure, you should update the schema stored in /sql folder.

![](/files/-M71kBodX8ccQL8iaLNM)

*Figure 17: Module schema file (Admin side)*

This is how the schema file looks like. It will make updates from version to version much easier.


---

# 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://xoops.gitbook.io/modulebuilder-tutorial/2administration/migrate.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.