Use this guide to move an existing DHRU Fusion 7 website to Fusion Core while keeping its database and supported customer files. This is a migration of your existing website. Do not create a fresh database or run the new-installation form against your live data.
For a website already running Fusion Core, use Self Update.
Plan the migration
Check the Fusion Core system requirements and obtain the official full Fusion Core package from your Dhru account. Have a legacy Full Access administrator account ready, including its authenticator code if enabled, and an eligible Fusion Core service for activation.
Arrange a maintenance window with your hosting provider or developer. Rehearse the migration using a copy of the actual database and customer files before changing the live website, especially if you use custom themes, payment modules, or other custom code. Confirm the supported migration path with support if your installation is older than Fusion 7.
1. Pause activity and make a complete backup
Pause the old website and its scheduled tasks. Stop external jobs that can change its database while you take the final backup and migrate it.
Back up the entire existing database and website files to a secure location outside the folders you will replace. Confirm that the backup can be restored. Keep the old configuration, customer downloads, gallery images, and any custom modules.
The wizard offers a database backup, but that is not a complete website backup. Keep your independent full backup throughout the migration and verification.
2. Preserve the legacy folders
Keep these folders in their original locations in the old website's public document root:
public_html/configs/
public_html/download/
public_html/images/gallery/If the site has custom payment gateway modules, also preserve:
public_html/modules/gateways/The wizard uses the old configuration to connect to the existing database and copies supported customer downloads and gallery images into Core's storage. Keep the original folders until the migration has finished.
Do not assume an old custom theme or PHP module will run unchanged in Fusion Core. Keep it in your backup and arrange any required conversion separately.
3. Replace the old application files
With the complete backup secured, remove the old application code while preserving the folders above. Upload the complete official Fusion Core package, keeping DhruFusionCore beside public_html, and point the domain to the package's public_html folder.
Do not leave old executable application files mixed with the new package. If you cannot confidently separate old application code from customer files, have your host or developer perform this step.
Before exposing the new document root, ensure direct web access to the preserved configs, download, and images paths is blocked. The supplied Apache .htaccess provides these restrictions when the server honors it. nginx requires equivalent configuration; ask your host to apply it before proceeding.
For a preserved custom gateway folder, the server must route /modules/ requests through Fusion Core rather than execute the old PHP files. This also matters for existing payment callback URLs.
Have your host verify that a direct request to a known preserved private file returns 403 or 404. An empty page from a PHP file is not proof that the folder is protected.
4. Follow the upgrade wizard
Open https://your-domain.example/setup/ on the final HTTPS website address. With the preserved legacy configuration in place, setup opens the legacy upgrade flow.
- Sign in with the legacy Full Access administrator. Enter its authenticator code if required.
- Review the backup screen and website address. Confirm the complete backup you prepared.
- Select Pause site and continue when prompted.
- Keep the page open while database changes and customer-file copying progress.
- Set a new administrator password when asked and finish the upgrade.
At the final check, the wizard moves the preserved configuration, download, and images folders outside the public document root and retains them for recovery. Preserved custom gateway code is moved into private storage for conversion. PHP must be allowed to move these folders into the parent directory. If this fails, keep the site paused, correct permissions with your host, and use the offered retry.
Use the final Reopen website action if it is shown. If setup instead shows the new-installation database form, stop and have the preserved configuration and folder layout checked. Do not enter the live legacy database into that form.
5. Activate and review Core
Sign in to the Core Admin panel with the new password. Complete any license-activation prompt through Connect Dhru V2, using the eligible Core service in your Dhru account.
Review the business identity, region, SMTP/email delivery, security, billing, and storefront settings. Supported legacy settings are imported, but customizations need review. Configure administrator roles and email templates for Core.
Review automation and install the commands or URLs generated by Core. Do not restart the old legacy cron commands. Confirm that the new jobs actually run.
6. Review payment gateways
Open Payment Gateways in Admin and review any legacy gateways offered for Import. Their old activation does not automatically mean they are ready to accept payments in Core.
- PayPal needs REST API credentials; the legacy email-based checkout is not enough.
- Stripe needs its webhook signing secret before the imported account can be enabled.
- PayerOne can carry over its token; verify the imported account and settings.
- Instructions-only payment methods can become offline payment accounts.
- Custom checkout modules need conversion to the Fusion Core gateway format.
Check callback/webhook configuration and verify each payment method before making it available to customers.
7. Verify the migrated website
Before returning to normal trading, check:
- Administrator and customer sign-in, including required security checks.
- Customer records, balances, services, prices, and order history.
- Customer downloads and gallery images from the actual old website.
- Supplier connections and the order workflows you use.
- Payment methods, callback handling, and email delivery.
- Storefront pages and the new automation schedule.
Keep the full pre-upgrade backup and preserved originals until verification is complete. Take a new complete backup after the migrated website has been checked.
If the upgrade stops
Reopen /setup/ and review its saved progress. Use an offered retry only after resolving the reported problem. If database progress is unknown or the wizard requests support, keep the site paused and contact DHRU Support with the error and reference.
Do not repeatedly start the migration, remove its saved state, delete the new DhruFusionCore/config/.env, or run SQL copied from another installation. Some database changes may already be committed.
If you need to return to the old website, restore the matching pre-upgrade database and files together with your hosting provider. Restoring only the old PHP files over a migrated database is not a rollback.