> For the complete documentation index, see [llms.txt](https://docs.mikopbx.com/mikopbx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mikopbx.com/mikopbx/english/faq/setup/change-host/transfer-using-backup.md).

# Transfer Using Backup

A method to transfer MikoPBX to another host using backup

This method involves creating a backup of your current MikoPBX configuration, transferring it, and restoring it on the new server. It’s simple to implement and suitable for small systems. This approach is convenient for users with minimal technical experience.

1. First, create a backup of your previous system. You can find detailed instructions in [this article](/mikopbx/english/modules/miko/module-backup.md).

<figure><img src="https://835495363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsZ8acWnNlSalIHQjMFu1%2Fuploads%2FRmaivLYpih6rh7zQK8PV%2FcreateBackupCopy.png?alt=media&amp;token=78a0cae9-2d9c-4767-84f2-e8f906e7bab9" alt=""><figcaption><p>Creating a new backup copy</p></figcaption></figure>

2. Select the data you want to transfer and wait for the process to complete.

<figure><img src="https://835495363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsZ8acWnNlSalIHQjMFu1%2Fuploads%2F5L3WOAJo4LUCueE2VqtV%2FselectingData.png?alt=media&amp;token=c323f34c-02c1-4f20-93a6-591fdeac376e" alt=""><figcaption><p>Selecting data for backup copy</p></figcaption></figure>

3. Download your archive by clicking the corresponding button in the **"Backup Module"** section:

<figure><img src="https://835495363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsZ8acWnNlSalIHQjMFu1%2Fuploads%2FyaDSYrWq5IjvvZ6eEnEr%2FselectingData2.png?alt=media&amp;token=8023d7c0-cb21-44a6-b6a6-31ebac26423e" alt=""><figcaption><p>Button to download archive</p></figcaption></figure>

4. On the new host (server) with your MikoPBX installation, restore from the archive by clicking **"Upload backup file"**:

<figure><img src="https://835495363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsZ8acWnNlSalIHQjMFu1%2Fuploads%2F8mfXriIRLL04nkbZszO9%2FuploadBackupFile.png?alt=media&amp;token=6a40a77d-15d9-42fb-a75e-880f17cc04e8" alt=""><figcaption><p>"<strong>Upload backup file</strong>" button</p></figcaption></figure>

After this, your system will be restored from the archive. This method is ideal for transferring small amounts of data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mikopbx.com/mikopbx/english/faq/setup/change-host/transfer-using-backup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
