Migrating to a New Server

Overview

When moving RISE CRM to a new server, you should migrate both the Rise Audit Pro files and the related database tables.

What this article explains

This article explains how to move the plugin safely during a server migration.

Why it is useful

• It helps preserve existing audit history.
• It reduces migration-related support issues.
• It gives administrators a checklist for verifying the plugin after migration.

Who should read this?

Server Administrator, RISE Admin, Developer / Support Engineer.

Where to find it

Old server plugin folder, new server plugin folder, database backup, and Rise Audit Pro → Plugin Health.

How to use it

1. Put the old CRM into maintenance mode if needed.
2. Export the full database from the old server.
3. Copy the Rise Audit Pro plugin folder from the old server.
4. Upload the plugin folder to the same plugin path on the new server.
5. Import the database into the new server.
6. Confirm RISE CRM works correctly.
7. Open Plugin Health and check database tables and system status.

Example workflow

After moving to a new hosting server, the administrator opens Plugin Health and confirms that all required tables exist and that existing log records are still visible.

Plugin folder path

/plugins/rise_log_pro/

After migration checklist

• Dashboard loads.
• Activity Log records are visible.
• Auth Log records are visible.
• Settings are preserved.
• Webhook URLs still point to valid endpoints.
• Scheduled reports and cron-related features are checked.

Screenshot

Common mistakes

• Copying plugin files without migrating the database.
• Migrating the database but forgetting plugin files.
• Forgetting to test webhook and report settings after a domain or SSL change.

Related articles

• Installation and Activation
• Plugin Health Overview
• Webhooks Overview
• Updating Rise Audit Pro