Getting started

Monitor PostgreSQL Assistant is available in the Monitor server folder (Monitor.PostgreSQL.Assistant.exe). The assistant guides you through the migration process step by step. You can open it as often as needed to check the status of your companies, and you can run the migration for each company when it is ready.

A prerequisite for the tool to function correctly is that Monitor ERP is updated to version:

  • 26.4.17

  • 26.5.8

  • or a later version

Step 1: Instructions

Start by reading the instructions on this help site. They explain each step of the migration process and help you prepare before making any changes.

Step 2: Setup PostgreSQL

Next, install PostgreSQL or connect to an existing PostgreSQL server. If PostgreSQL is not already installed, click Setup PostgreSQL and follow the wizard to install it locally.

If PostgreSQL is already installed, the assistant will normally connect automatically and mark the Setup PostgreSQL step as completed.

Read the installation guide

Step 3: Prepare and migrate companies

This step shows a list of companies. Each company includes a set of checks that must be reviewed and approved by either Monitor or the customer before migrating a production company. The checks do not apply to Test companies, and they can be migrated even if the checks are not approved.

Before migrating production companies, review the following areas:

  • Custom Solutions: Verify that all custom solutions are ready (Read more)
  • Business Intelligence: Verify custom dashboards, reports etc. (Read more)
  • Options – Delivered by Monitor: Update your options to the specified versions (Read more)
  • Adaptations – Delivered by Monitor: Install Deployment Platform to get your adaptations delivered (Read more)
  • Customized Reports & Documents – Delivered by Monitor: Check that your report/document has been approved by Monitor (Read more)
Using Test companies
Use test companies to verify the migration process before migrating production databases. A test company only requires PostgreSQL to be configured; the migration can proceed without completing all preparation sections. This gives you a safe way to validate the process and test custom integrations before going live.

Step 4: Start the migration

When all preparation steps are complete, select the companies or test companies you want to migrate, then click Start Migration.

To view test companies, click the arrow next to the production company.

Please note! There is no option to select all companies at once. You must select each company individually.

The migration checks whether Monitor is running and prompts you to stop the Monitor Server service if needed. Make sure all users are informed that Monitor will be unavailable until the migration is finished. Confirm the dialog to begin the migration.

Please note! All companies in the same system will be unavailable during the migration. This does not apply when migrating test companies.

Important to note

  • Plan the migration during off-peak hours to minimize business impact

  • Make sure to have sufficient disk space available before starting the migration. At least twice the size of the original database. It’s also recommended to clean up old and unused databases. (Read more)

    Please note that the backup requires disk space equivalent to the total size of all databases (test-databases included), plus an additional amount of equal size during the replacement and renewal of the backup.

  • Estimate approximately 1 to 3 minutes per GB of database size

  • Test with a test company first before migrating production databases if needed

After the migration

After the migration is completed:

  • Make sure to store the password for the PostgreSQL user account in a safe location. This is the password you will need if you want to connect to your databases. You are solely responsible for storing the password, as Monitor does not save it.

  • Create a backup (Read more)

  • If you are using external servers or other clients that need to connect to the Monitor database server after the conversion to PostgreSQL, you must allow these connections in the pg_hba.conf file (Read more)

  • Postgres Configuration Manager can be used to optimize system performance when needed. (Read more)

  • Create any necessary test companies that have not been migrated (for example, daily copies).

  • When updating Monitor with PostgreSQL: Before starting an update, ensure that all test companies in IM / Company Config have been handled. If non-migrated test companies are not removed, there is a high risk that the update will fail.

    To avoid this issue: Remove any test companies in IM / Company Config that you do not plan to migrate.

    The underlying databases can remain if needed; only the company entries must be removed. (Read more)