> For the complete documentation index, see [llms.txt](https://docs.smartlauncher.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smartlauncher.net/products/faq/start-here/how-to-migrate-from-other-launchers.md).

# How to migrate from other launchers

At the moment, direct backup import is supported for **Nova Launcher** backups.

To migrate from Nova:

1. Create your backup in Nova Launcher.
2. Open the backup screen in Smart Launcher.
3. Select restore/import and choose the Nova backup file.

Smart Launcher can import that file from the same screen used for Smart Launcher backups, so the flow is the same.

After import, quickly check widgets and app shortcuts, then save a new Smart Launcher backup once everything looks right.

If you are coming from another launcher, you can still migrate smoothly by recreating the home layout manually and then saving it as a Smart Launcher backup.


---

# 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.smartlauncher.net/products/faq/start-here/how-to-migrate-from-other-launchers.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.