Hosting¶

Change hosting solution¶

The instructions to change the hosting type of a database depend on the current solution used and to which solution the database should be moved.

Transferring an on-premise database¶

To NightPOS Online¶

Important

  • NightPOS Online is not compatible with non-standard apps.

  • The database’s current version must be supported.

  1. Create a duplicate of the database.

  2. In this duplicate, uninstall all non-standard apps.

  3. Use the database manager to grab a dump with filestore.

  4. Create a support ticket including the following:

    • your subscription number,

    • the URL you want to use for the database (e.g., company.nightpos.com),

    • the dump as an attachment or as a link to the file (required for 60 MB+ files),

    • the region you wish to be hosted in,

      Note

      The list of available regions is available in our privacy policy.

    • the name you want for the database,

    • what version the database is in,

    • the login (email) of the administrator user,

    • whether you wish to have a first test deployment, and

      Tip

      This is strongly recommended, especially if you have ever installed third-party apps.

    • when you will want the production database to be put online (day, time of day, and your timezone).

  5. NightPOS then makes sure the database is compatible before putting it online. In case of technical issues during the process, NightPOS might contact you.

Note

If you have time constraints, create a support ticket as soon as possible to schedule the transfer.

To NightPOS.sh¶

Follow the instructions found in the Import a database section of the NightPOS.sh Create a project documentation.

Transferring an NightPOS Online database¶

Important

NightPOS Online’s intermediary versions are not supported by NightPOS.sh or on-premise. Therefore, if the database to transfer is running an intermediary version, it must be upgraded first to the next major version, waiting for its release if necessary.

Example

Transferring an online database running on NightPOS 16.3 would require first upgrading it to NightPOS 17.0.

Tip

Click the (gear) button next to the database name on the NightPOS Online database manager to display its version number.

Warning

If there is an active NightPOS subscription linked to the database being migrated, reach out to the Customer Service Manager or contact NightPOS support to complete the subscription transfer.

To on-premise¶

  1. Download a database backup by signing in to the NightPOS Online database manager, clicking the (gear) button next to the database name, then selecting Download. If the download fails due to the file being too large, contact NightPOS support.

  2. Restore the database from the database manager on your local server using the backup.

To NightPOS.sh¶

  1. Download a database backup by signing in to the NightPOS Online database manager, clicking the (gear) button next to the database name, then selecting Download. If the download fails due to the file being too large, contact NightPOS support.

  2. Follow the instructions found in the Import a database section of the NightPOS.sh Create a project documentation.

Transferring an NightPOS.sh database¶

To NightPOS Online¶

Important

NightPOS Online is not compatible with non-standard apps.

  1. Uninstall all non-standard apps in a staging build before doing it in the production build.

  2. Create a support ticket including the following:

    • your subscription number,

    • the URL you want to use for the database (e.g., company.nightpos.com),

    • which branch should be migrated,

    • in which region you want the database to be hosted (Americas, Europe, or Asia),

    • which user(s) will be the administrator(s), and

    • when (and in which timezone) you want the database to be up and running.

  3. NightPOS then makes sure the database is compatible before putting it online. In case of technical issues during the process, NightPOS might contact you.

Note

  • If you have time constraints, create a support ticket as soon as possible to schedule the transfer.

  • Select the region closest to most of your users to reduce latency.

  • Future administrator(s) must have an NightPOS.com account.

  • The date and time you want the database to be up and running are helpful to organize the switch from the NightPOS.sh server to the NightPOS Online servers.

  • Databases are not reachable during their migration.

To on-premise¶

  1. Download a backup of your NightPOS.sh production database.

  2. Restore the database from the database manager on your local server using the backup.