> 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/trackers-migration-from-wialon.md).
# Trackers migration from Wialon
Migrate devices from Wialon to Navixy in bulk using exported device information. Map Wialon fields to Navixy fields and choose whether to send configuration commands.
After you have transferred your users, you need to migrate devices from the Wialon system. Thanks to the [Bulk activation](/docs/admin/devices/bulk-activation.md) device migration is quick and convenient.
1. In Wialon CMS, open the units:
In the "Select" column, select the element from which you want to save data to a file. To select multiple items, use the Ctrl key (for a range of items).
2. Next, you need to select the necessary fields to load. Click ... and add all required columns for export:\ 
To import devices into the Navixy platform the following information is required:
| File | Navixy | Wialon |
| ------------- | -------------------------------- | ----------- |
| user\_id | User ID | - |
| model | Model | Device type |
| label | Name | Name |
| device\_id | device's IMEI | ID |
| phone | Phone number (with country code) | Phone |
| apn\_name | APN name | - |
| apn\_user | APN user | - |
| apn\_password | APN password | - |
| comment | Comment | - |
The APN settings depend on your device's SIM GSM carrier. It is desirable to specify these data. However, if you will change the IP address and ports of the devices manually, this data is not necessary.
4. To export data, use the .xlsx button in the lower right corner of the table:
5. Download the [example file](https://cdn.navixy.com/hardware_trackers_activation_example_2781a794af.csv) for importing devices to Navixy platform and transfer all fields from the Wialon file. Specify a user\_id as a name, where to load devices.
6. Contact Navixy Technical Support and request to transfer devices. In order to make the migration as fast and convenient as possible, please specify the following information:
* To send/not to send registration commands to devices.
* If you choose "send" - commands with server and port settings will be sent to all devices, as well as other commands with the platform's default settings. Packet sending mode, sleep mode, events and other devices' settings will be affected.
* If you select "do not send" - devices will just be registered in the system under users that are specified in the file name. To connect your devices to the platform, change the IP address and port manually. A different port number is used for all manufacturers. See what port number to specify on the next page:\
[Supported GPS Trackers — Navixy](https://www.navixy.com/devices/).
* Attach a file with filled information and user ID as a name.
After devices transferring, some sensors and rules will be created automatically. Types and number of sensors and rules depend on the device model.
---
# 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://navixy.com/docs/on-premise/qa/migrating-users/migrating-from-wialon/trackers-migration-from-wialon.md?ask=&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.