Breadcrumbs

Upgrading GlobalForms

Move an existing GlobalForms 10 server to the current release. Once upgraded, the server keeps itself up to date with automatic updates.

Do you need this page?

Look in your GlobalForms install folder (C:\GlobalForms by default):

If the install folder…

Then

Contains launcher.js and install-info.json

Your server already uses automatic updates and stays current on its own. See Automatic Updates. You only need the upgrade order below.

Does not contain launcher.js

Your server was installed with an earlier installer. Follow this page once to upgrade it. After that, updates are automatic.

Upgrade order with GlobalCapture

If GlobalForms and GlobalCapture use the same MongoDB server, always update GlobalCapture first, then GlobalForms.

Before you begin

  • Check that the server meets the System Requirements, including Node.js 24 and MongoDB 8. If MongoDB is older, upgrade it first, following MongoDB's upgrade instructions.

  • Plan a maintenance window. GlobalForms is unavailable during the upgrade.

  • Have an account with local administrator rights on the server.

Step 1: Back up

  1. Back up the GlobalForms database in MongoDB, using your usual MongoDB backup tools.

  2. Stop the GlobalForms service in Services.

  3. Copy the whole install folder (for example C:\GlobalForms) to a safe location. Make sure the copy includes:

    • config\ (your settings)

    • ssl\ (certificates)

    • files\ (uploaded attachments) and PDFsnapshots\

    • any files you added to the program folders, such as images, scripts or resources in client\dist

Step 2: Install Node.js 24

Download and install Node.js 24 or later from nodejs.org. Open a new PowerShell window and run node --version to confirm it.

Step 3: Run the installer over your existing installation

  1. Open PowerShell as administrator and download the installer:

    PowerShell
    mkdir C:\Temp\GlobalFormsSetup
cd C:\Temp\GlobalFormsSetup
Invoke-WebRequest "https://update.square9.cloud/globalforms/releases/bootstrap-installer.js" -OutFile ".\bootstrap-installer.js"
node .\bootstrap-installer.js

  2. When asked for the Install path, enter your existing install folder.

  3. Setup detects the existing installation and loads its settings, including the domain and MongoDB connection, as defaults. Check each value and press Enter to keep it.

  4. When asked to overwrite files in the existing location, answer Yes.

  5. Enter the root admin details. Use the existing administrator's name and email.

  6. If setup reports that a GlobalForms service already exists, answer Yes to replace it.

Setup moves your existing settings into config\local.json, installs the current release, registers the GlobalForms Forms Server service and starts it. Automatic updates are turned on, using the Stable channel.

Step 4: Check the upgrade

  1. Open Services and confirm GlobalForms Forms Server is Running and set to Automatic.

  2. If an older GlobalForms service is still listed, stop it and set its startup type to Disabled, so it does not compete for the same ports.

  3. Sign in to GlobalForms and open a few forms and submissions.

  4. If you use HTTPS, open the HTTPS address and confirm the certificate is still in use.

  5. Copy back any files you added to the program folders (see Step 1), then check the forms that use them.

  6. Test any integrations: GlobalCapture, single sign-on and SQL data sources.

After upgrading

  • Settings: make all future changes in config\local.json. See Configuration Files.

  • Client configuration file: you no longer need to edit client\dist\config.js for the server address or HTTPS. Earlier changes to that file are not needed.

  • Updates: new releases install automatically during the maintenance window. To change the window or channel, see Automatic Updates.

  • Release notes: review the Release Notes for the versions you skipped, especially behavior changes.

If something goes wrong

  1. Stop the GlobalForms Forms Server service.

  2. Restore the install folder from your Step 1 copy, and the database from your MongoDB backup if needed.

  3. Start your original GlobalForms service.

  4. Contact Square 9 Support with the contents of the logs folder from the upgrade attempt.

Troubleshooting

Symptom

Cause and fix

Node.js 24+ is required

Install Node.js 24 or later and open a new PowerShell window.

Setup can't connect to MongoDB

Check the MongoDB connection values setup loaded, and that MongoDB is running and is version 8 or later.

The new service won't start, or the port is in use

An older GlobalForms service may still be running. Stop and disable it, then start GlobalForms Forms Server.

A setting you changed before the upgrade is missing

Compare config\local.json with the config folder in your backup, and add the missing setting to local.json.

Images or resources used by a form are missing

Copy the files you added to client\dist back from your backup.