> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/on-premise/qa/migrating-users/migrating-from-wialon/geofences-migration-from-wialon.md).

# Geofences migration from Wialon

Geofences can be migrated seamlessly from Wialon to Navixy, allowing your users to continue using them without disruption. To transfer geofences to your users, follow the instruction below.

1. Open user account in Wialon and click on the username in the upper right corner:

![](/files/4BEK5ZOaHRnPw3ZGVrCO)

2. Select Export to KML/KMZ

![](/files/tYNMeAuU3Fia4rddbMKi)

3. Select all required geofences to transfer and press OK.

![](/files/Dl5Gy1Ht68FtAxLMqEHC)

4. Open a user account in Navixy admin panel.

![](/files/mliF9KNulxHWKiPabejU)

5. And activate geofences section here.

![](/files/G6jfGKybKOP92Uxe8vvu)

After pointing the cursor over the geofence import, two import options will be displayed. Choose import geofences from a KML file:

![](/files/0ckYAcWUhPZYszJaVhO5)

6. Add the exported file and specify the default radius for circle geofences.

For polygon geofences, the import will be done exactly as in the Wialon system. For circle geofences, the centers with radiuses specified in the previous step will be transferred. After that, you might need to change the radius of geofences manually. Place the cursor on the required geofence and press the pencil button that appears.

![](/files/6TAIVUOrLtKgoveUaZY7)

After transferring geofences, they can be used for rules and analytics on the Navixy platform.


---

# 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 dynamically by asking a question.

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

```
GET https://navixy.com/docs/on-premise/qa/migrating-users/migrating-from-wialon/geofences-migration-from-wialon.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.