> 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.md).

# Q\&A

- [PaaS](https://navixy.com/docs/on-premise/qa/paas.md): Deploy Navixy as a PaaS cloud service by creating an instance through the customer portal. Manage the platform via the admin panel without managing server infrastructure.
- [PaaS vs. On-Premise](https://navixy.com/docs/on-premise/qa/paas-vs-on-premise.md): Compare Navixy PaaS and on-premise deployment across 18 criteria including updates, hosting, security, support, video telematics, and data warehouse capabilities.
- [Subscription fees](https://navixy.com/docs/on-premise/qa/subscription-fees.md): Understand Navixy subscription billing based on active devices, payment deadlines, and service suspension rules for both PaaS and on-premise instances.
- [Software updates](https://navixy.com/docs/on-premise/qa/software-updates.md): Keep Navixy up to date on PaaS or on-premise. Covers update frequency, eligibility requirements, and links to OS-specific update procedures for Linux and Windows.
- [Current version](https://navixy.com/docs/on-premise/qa/software-updates/current-version.md): Find the Navixy on-premise platform version number in the VERSION file on your server. Understand the major and minor build numbering scheme.
- [Migrating users](https://navixy.com/docs/on-premise/qa/migrating-users.md): Migrate users to Navixy from another instance or vendor using data forwarding. Covers user account creation, device configuration, and data synchronization setup.
- [Migrating from Wialon](https://navixy.com/docs/on-premise/qa/migrating-users/migrating-from-wialon.md): Migrate from Wialon to Navixy with guides for users, geofences, trackers, and sensors. Each guide covers the export and import steps for that data type.
- [Users migration from Wialon](https://navixy.com/docs/on-premise/qa/migrating-users/migrating-from-wialon/users-migration-from-wialon.md): Export users from Wialon and import them into the Navixy Admin panel. Use the template file format with required fields: email, password, and account status.
- [Geofences migration from Wialon](https://navixy.com/docs/on-premise/qa/migrating-users/migrating-from-wialon/geofences-migration-from-wialon.md): Export geofences from Wialon as KML or KMZ files and import them into Navixy. Covers polygon and circle geofence handling with custom radius configuration.
- [Trackers migration from Wialon](https://navixy.com/docs/on-premise/qa/migrating-users/migrating-from-wialon/trackers-migration-from-wialon.md): 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.
- [Tracker data](https://navixy.com/docs/on-premise/qa/migrating-users/migrating-from-wialon/trackers-migration-from-wialon/tracker-data.md): Transfer Wialon tracker data history and sensor calibration to Navixy using the Wialon Retranslator tool. Configure retranslation and handle trip history import.
- [Sensors migration from Wialon](https://navixy.com/docs/on-premise/qa/migrating-users/migrating-from-wialon/sensors-migration-from-wialon.md): Copy sensor configurations from Wialon to Navixy in bulk and import calibration tables via CSV files. Use Navixy sensor migration tools to transfer settings.


---

# 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.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.