Supported Migrations
ORIV’s free migration service is exclusively available for WordPress-powered websites. If your site runs on a different CMS or platform, this migration pathway will not apply. All migration requests are handled through a queue-based system. Rather than processing all requests simultaneously, ORIV completes migrations in small daily batches. This deliberate approach serves two important purposes: it gives you adequate time to thoroughly test each migrated site before making it live, and it minimizes the risk of errors or service disruptions — particularly when you’re migrating multiple sites at once.Step 1: Submit Your Migration Details
The migration process begins once ORIV receives your request. You’ll be provided with a shared Google Sheet where you can enter all the necessary details for each site you want to migrate. Completing this form accurately and thoroughly is the single most important thing you can do to prevent delays.Information Required for Each Site
For every WordPress site included in your migration request, please provide the following details:- Full WordPress admin login URL (e.g., yourdomain.com/wp-admin)
- WordPress admin username with full administrative privileges
- The email address associated with the admin account
- The admin account password (shared securely via the Google Sheet)
- The destination server IP address where the site should be migrated
- The PHP version your site requires (e.g., PHP 8.1, 8.2)
- Any additional notes, special configurations, or custom requirements
How to Share Admin Access Securely
If you’re uncomfortable sharing your primary WordPress admin credentials, ORIV recommends creating a temporary admin user specifically for the migration. This approach keeps your main account secure while still giving the migration team the access they need. To set this up:- Log in to your WordPress dashboard and navigate to Users → Add New
- Create a new user with the Administrator role
- Use support@oriv.cloud as the email address for this temporary account
- After the migration is fully complete and verified, delete this temporary user
Step 2: Migration Queue & Scheduling
Once your site details have been submitted, your migration request is added to ORIV’s processing queue. Migrations are completed in controlled daily batches rather than all at once. This structured scheduling ensures:- No unnecessary downtime for your live site during the migration window
- Sufficient time to test and verify each migrated site before proceeding to the next
- A smoother, more predictable experience — especially valuable when migrating multiple sites in succession
Step 3: Migration in Progress
When your site reaches the front of the queue and migration begins, the process is handled entirely by ORIV’s team. Here’s what you should know about what happens during this stage.What Happens During Migration
- Zero downtime: Your live site continues to operate normally throughout the entire migration. Visitors will not experience any interruptions.
- Temporary demo domain: Your site is migrated to a temporary demo domain provided by ORIV, not directly to your live domain. This allows thorough testing before any DNS changes are made.
- Live domain stays untouched: Your original domain and hosting remain completely unaffected until you explicitly decide to switch over.
What to Avoid While Migration Is Underway
To ensure the migration produces an accurate copy of your site, please observe the following during this stage:- Do not make any content changes, plugin updates, or configuration adjustments on the source site. Changes made during migration may not be captured in the migrated copy.
- Expect temporary plugin deactivation: ORIV may temporarily disable certain security plugins (such as Wordfence or Sucuri) and caching plugins (such as WP Super Cache or W3 Total Cache) on the source site to facilitate a clean migration. These will be re-enabled once migration is complete.
Step 4: Migration Complete — Review & Testing
Once the migration is finished, ORIV will notify you and provide access to the migrated site on the temporary demo domain. This is your opportunity to conduct a thorough review before anything goes live.Your Post-Migration Testing Checklist
Take your time with this review. Carefully check the following areas:- Browse all pages, posts, and custom content types to verify that everything displays correctly
- Test all forms (contact forms, signup forms, checkout flows) to confirm they function properly
- Log in to the WordPress admin dashboard and review your settings, menus, and widget configurations
- Reactivate any premium or licensed plugins that were deactivated during migration, and verify their license keys are active
- Check media files (images, videos, PDFs) to ensure they loaded correctly and are not broken
⚠️ Critical Reminder:
- Do NOT delete your source site immediately after migration. Keep it fully intact for at least two weeks as a safety net.
- Make sure you have verified backups of the original site before removing it from your previous host.
- If you discover any issues during testing, contact ORIV support immediately so the team can investigate and resolve them quickly.
Step 5: Going Live on ORIV
After you’ve completed your testing and confirmed that everything on the migrated site is functioning correctly, ORIV will assist you with the final steps to make your site live on its new home.The Go-Live Process Includes
- DNS update: Updating your domain’s DNS records to point to the new ORIV server. This redirects all traffic to the migrated site.
- SSL installation and verification: Ensuring your site is served over a secure HTTPS connection with a valid SSL certificate.
- Basic performance checks: Running initial diagnostics to confirm the site loads efficiently on the new server.
- Backup activation: Setting up automated backups on ORIV to protect your site going forward.
Alternative Migration Methods
In some situations, the standard migration approach may not work as expected — for example, if your current host has non-standard configurations, restricted access, or particularly large databases. When this occurs, ORIV may need to use an alternative migration method. This typically involves creating a full backup archive directly on your source server and transferring it to ORIV. Before proceeding with this approach:- ORIV will explain why the standard method was not viable and request your explicit permission before using the alternative approach.
- You’ll need to confirm that your source server has sufficient disk space available to generate the backup archive (typically 2–3x the size of your site).
- ORIV will keep you informed at every stage of the alternative process, so you’re never left guessing.
When Migration Cannot Be Completed
In rare cases, a migration may not succeed despite the team’s best efforts. If this happens, ORIV will:- Provide a clear, detailed explanation of why the migration failed and what technical obstacles were encountered.
- Present all available alternative options, including manual migration approaches or third-party tools that may help.
- Outline any additional access, credentials, or server-side changes that might be required to attempt the migration again.