In order to improve NexoPOS, we usually each month push an update on the system. Most of these update include files changes, which can improve the layout, offer new features or adjust existing. We perform these operation to improve the user experience. However, an update might also include a database migration, and it’s really important for those already using NexoPOS. So we’ll see what it’s all about and how  to handle the migrations.

Let’s get started.

What is the database migration on NexoPOS

As the name might suggest, a database migration is the process by which a database has his schema updated. This  ensure the database is seamlessly compatible with the files update. This process does not apply to those installing the system for the first time, since the database schema is updated there as well.

A database migration is progressive, this mean that no matter from which version you’re using NexoPOS, you can start using the latest update. For example let’s assume you had the version 1.0 and don’t update the script till the version 3.0 (with 10 version between both version). The migration will run from the version 1.0, going through all the migration files between both versions, to the last version migration.

We do make sure that within the process, nothing occur and that your informations aren’t lost. It’s however advised to make a backup of your system before doing that.

How to make a database migration on Tendoo CMS

We would like to remind you that NexoPOS itself is a module of Tendoo CMS. So, the migration process is made from Tendoo CMS. The migraiton might be for NexoPOS, Gastro or any of our modules. Usually, you need to access (after an update) to the module page and check if there is a migration available. Note that, we do usually mention on the changelog if the update require or not a migration. The process is now simple. Just go to the modules, then search for the database icon and click on that to proceed to the database migration.

Now you can test your system and check if everything works correctly. If not, please quickly let us know at [email protected] or on the WhatsApp community group.

Running a migration manually

For some reason, we might suggest you to run a migration manually from a specific version to have an issue fixed. A manual migration is the process by which you enter a URL on your browser which containt the verison from which the migration should start. You should be logged in on NexoPOS and the URL should have the following shape :

Note that here, we’re migrating the module “nexo” (it’s the namespace of NexoPOS) from the version 1.0. So here, the migration will run from the version 1.0 to the last version (it might be 3.14.11). Don’t forget to replace “” with your actual domain name.

Note that, the migration has a validity, which mean that, if you’re for example still using NexoPOS 2.8.2 and would like to migrate to 3.14.11. It’s impossible since the old migration files might have been deleted from the script. In such situation, we invite you to get in touch with us or proceed to an export/import operation.

Can i still use the system without migration ?

It’s possible, but it’s strongly not recommended. If you still use the system like that, it might throw error and you won’t be able to process using the system. Note that all error aren’t visible on the screen. Most of the error occur on the background using an asynchronous process. We’re most advised to discover what’s wrong. That’s why you should always get in touch with us if something get wrong.