Upgrade Guide: V1 to V2

Last updated: July 11th, 2025

Prerequisites

The following are the prerequisites required to run the application:

Before proceeding, please download the latest version of JupiterMeet Pro V2 from CodeCanyon.

If you have any questions or face issues during the upgrade process, feel free to contact our support team at any time. Please ensure your support plan is active. If it's not, you can activate or renew your support via the link below:
👉 Activate Support

Database Migration

To ensure a smooth and safe migration of your existing V1 database to the new V2 codebase, please follow the steps outlined below.

Before proceeding, we strongly recommend taking a full backup of your V1 database. This will allow you to restore your data in case anything goes wrong during the migration process.
Also, please ensure that your V1 installation is updated to the latest version, i.e., v1.8.8, before starting the migration.

Install V2

Begin by installing the V2 version of the application using the provided setup wizard.

Open yourdomain.in/install in the browser to install V2.

Export Migration Table

After V2 is successfully installed, export the migrations table from the V2 database.

Step - 1

Step - 2

Replace Migration Table

Delete the existing migrations table from your V1 database.

Import the previously exported migrations table from V2 into your V1 database

Delete Migration Entries

Remove entries from the migrations table as mentioned below to prevent migration conflicts.

Run Migrations

Execute the following command to apply the remaining migrations.

In your .env file, the DB_DATABASE variable is currently set to the v2 database. Please update it to the v1 database name instead and then run the below command.

php artisan migrate

Update NodeJS Module

The required environment variables for NodeJS are already defined in your /server .env file.

Copy the relevant values from the .env file and paste them into the appropriate fields under: Admin > Settings > NodeJS Module

Done! Your database has been successfully transitioned from V1 to V2.

To retain your avatars, please move the contents of the public/storage/avatar directory from your previous codebase to the new one.