The Zero-Downtime Website Migration Checklist for Nepali E-commerce with Payment Integration
Migrating your Nepali e-commerce website, especially one that processes payments via Khalti, eSewa, and bank transfers, demands a meticulous approach to ensure zero downtime. A successful website migration involves careful planning, thorough backups, precise cPanel transfers, and strategic DNS cutovers to maintain continuous service for your customers.
Key facts: * Downtime Cost: According to a 2024 report by Statista, even a few hours of e-commerce downtime can cost small businesses thousands of NPR in lost sales and customer trust. * Payment Gateway Integration: Ensure Khalti and eSewa API keys and callback URLs are correctly configured post-migration. * DNS Propagation: DNS changes can take up to 48 hours to fully propagate across Nepal, requiring a strategic cutover plan. * Backup Importance: Always have multiple, verified backups before initiating any migration. * Provider Choice: Opt for a hosting provider like Hosting Nepal that offers expert migration assistance.
Phase 1: Pre-Migration Planning and Preparation
Thorough preparation is the cornerstone of a successful, zero-downtime website migration. This phase focuses on gathering all necessary information, performing initial checks, and securing your existing data.
1. Initial Assessment and Inventory
Before touching any files, understand your current website's structure and dependencies. Document everything to avoid surprises.
* Website Audit: List all pages, posts, products, images, and media files. Note any custom code or plugins, especially those related to Khalti, eSewa, or bank transfer integrations. Check your current WordPress version and PHP version. * Hosting Environment Details: Gather login credentials for your current cPanel, FTP, and database. Note your current web server (Apache, Nginx, LiteSpeed) and PHP configuration. Understanding these details helps ensure compatibility with your new hosting environment. * Domain and DNS Information: Confirm your domain registrar and access details. Identify your current Nameserver settings and Time-To-Live (TTL) values for DNS records. A lower TTL (e.g., 300 seconds) can significantly speed up DNS cutover later. * Payment Gateway Configuration: Document all Khalti, eSewa, and bank transfer integration settings. This includes API keys, merchant IDs, callback URLs, and any custom payment success/failure pages. These are critical for maintaining continuous payment processing post-migration.
2. Comprehensive Backup Strategy
Backups are your safety net. Never proceed with a migration without multiple, verified copies of your website data.
* Full cPanel Backup: Utilize your current cPanel's backup utility to create a full website backup, including all files, databases, email accounts, and configurations. Download this backup to your local machine. * Database Backup: Export your WordPress database separately using phpMyAdmin or a plugin. This provides an additional layer of security for your critical e-commerce data. * Files Backup (FTP/SFTP): Use an FTP client (like FileZilla) to download all website files from your public_html directory. This ensures you have a raw copy of your site's structure and content. * Verify Backup Integrity: Crucially, test your backups. Attempt to extract a few files or import a small database segment on a local development environment to ensure they are not corrupted. According to industry best practices, at least two separate backup copies should be stored in different locations.
3. New Hosting Setup and Preparation
Prepare your new hosting environment to receive your website. This includes setting up your domain and ensuring compatibility.
* Choose a Reliable Host: Select a hosting provider known for performance and support in Nepal, like Hosting Nepal. Ensure they offer cPanel, sufficient resources (SSD storage, RAM), and good uptime for e-commerce sites.
* New Hosting Account Setup: Create your new hosting account and ensure cPanel access. Set up a temporary domain or subdomain on the new server (e.g., dev.yourdomain.com.np) for testing purposes before the live cutover.
* Database Creation: Create a new MySQL database and user in your new cPanel. Note down the database name, username, and password, as these will be needed for your wp-config.php file.
* PHP Version and Extensions: Ensure the new server's PHP version matches or is newer than your current site's (e.g., PHP 8.1 or 8.2 for modern WordPress). Confirm all necessary PHP extensions (like mysqli, curl, gd) are enabled for WordPress and WooCommerce.
Phase 2: Migration Execution and Verification
This phase involves transferring your website files and database, configuring the new environment, and rigorously testing everything before the final DNS cutover.
1. Transferring Website Files and Database
Moving your website's core components to the new server.
* cPanel to cPanel Transfer (Recommended): If both your old and new hosts use cPanel, the easiest method is to provide your new host (e.g., Hosting Nepal) with your old cPanel login details. They can often perform a full account transfer, including files, databases, and email accounts, with minimal effort on your part.
* Manual File Transfer: If a cPanel-to-cPanel transfer isn't possible, upload your backed-up website files via FTP/SFTP to the public_html directory of your new hosting account. Import your database backup using phpMyAdmin in the new cPanel.
* Update wp-config.php: Edit the wp-config.php file in your new public_html directory to reflect the new database name, username, and password you created in the new cPanel. Also, ensure the AUTH_KEY, SECURE_AUTH_KEY, etc., are consistent or regenerated for security.
* WordPress URL Update: After importing the database, update all instances of your old URL to the new temporary URL (e.g., dev.yourdomain.com.np) within the database. Tools like Search-Replace-DB or plugins like Better Search Replace can help with this. This step is crucial for WordPress migration.
2. Configuration and Testing on New Server
Before going live, thoroughly test your migrated site on the temporary URL.
* Access Temporary URL: Ensure you can access your website using the temporary domain or by modifying your local hosts file to point your domain to the new server's IP address. This allows you to test the new site without affecting the live one. * Thorough Website Functionality Test: Navigate through all pages, posts, and product listings. Test forms, search functionality, image loading, and internal links. Crucially, test the entire e-commerce checkout process, from adding items to the cart to initiating payments via Khalti, eSewa, and bank transfer. Confirm that payment gateways redirect correctly and process transactions on the test environment. * Payment Gateway Re-configuration: Double-check Khalti and eSewa API keys, merchant IDs, and callback URLs. Update these if necessary, especially if the new server's IP address or environment requires it. Ensure the payment success/failure pages are loading correctly. * Email Testing: If you migrated email accounts, send and receive test emails to ensure they are functioning correctly on the new server. * Performance Check: Use tools like GTmetrix or Google PageSpeed Insights on your temporary URL to assess the new server's performance. Identify and address any immediate performance bottlenecks.
Phase 3: DNS Cutover and Post-Migration Tasks
The final phase involves pointing your domain to the new server and performing essential post-migration checks.
1. Strategic DNS Cutover
This is the critical step where your website goes live on the new server.
* Lower DNS TTL: If you haven't already, lower your domain's DNS TTL (Time-To-Live) values to a short duration (e.g., 300 seconds or 5 minutes) at least 24 hours before the planned cutover. This minimizes propagation time.
* Update Nameservers/A Record: At the scheduled time, update your domain's Nameservers at your domain registrar to point to your new hosting provider's Nameservers (e.g., ns1.hostingnepal.com, ns2.hostingnepal.com). Alternatively, if you manage your DNS records directly, update the 'A' record for your domain to the new server's IP address.
* Monitor DNS Propagation: Use online DNS propagation checkers to track the spread of your new DNS settings across global and local Nepali internet service providers like WorldLink, Vianet, and Subisu. According to NTA 2025 data, average DNS propagation in Nepal can range from a few minutes to several hours, though it can sometimes take up to 48 hours.
2. Post-Migration Verification and Optimization
Once the DNS has propagated, perform final checks and optimizations.
* Live Website Verification: Access your live website from multiple devices and internet connections (e.g., Ncell, NTC) to confirm it's loading correctly from the new server. Clear your browser cache. * Full Functionality Test (Live): Repeat all functionality tests, especially the e-commerce checkout process with Khalti, eSewa, and bank transfers, on the live site. Make a small test purchase to ensure everything is working end-to-end. * SSL Certificate Installation: Ensure your SSL certificate is correctly installed and active on the new server. Verify that your site loads via HTTPS and that the padlock icon is visible in browsers. Hosting Nepal provides free Let's Encrypt SSL certificates. * Search Engine Optimization (SEO) Checks: * Google Analytics/Search Console: Verify that your Google Analytics tracking code is active and data is being collected. Check Google Search Console for any crawl errors or indexing issues. * XML Sitemap: Resubmit your XML sitemap to Google Search Console to encourage re-indexing of your new site. * Broken Links: Use a broken link checker to identify and fix any broken internal or external links that might have occurred during migration. * Old Hosting Account: Keep your old hosting account active for at least a week or two as a fallback. Once you are completely confident in the new setup, you can then proceed to cancel the old account.
Common Website Migration Issues and Troubleshooting for Nepali Websites
Even with a checklist, issues can arise. Knowing how to troubleshoot common problems can save significant time and stress.
1. Website Not Loading or Displaying Errors
* Incorrect wp-config.php: Double-check database credentials (name, user, password) and host (usually localhost). A typo here is a common cause of "Error establishing a database connection."
* Permissions Issues: Incorrect file and folder permissions can prevent the web server from reading files. Files should generally be 644 and directories 755. Use your cPanel file manager or FTP client to correct these.
* Missing Files/Database: Ensure all files are uploaded to the correct public_html directory and the database is fully imported. Check the size of your uploaded files against your backup.
* PHP Version Incompatibility: If your site uses an older PHP version and the new server runs a newer one, or vice-versa, certain functions might break. Adjust the PHP version in your cPanel or consult your host.
2. Broken Links and Images After WordPress Migration
* Database URL Mismatch: This is the most frequent cause. The WordPress database stores absolute URLs. If you didn't update them correctly during the migration, links and images will point to the old domain. Use a search-and-replace tool (like Better Search Replace plugin or WP-CLI) to update all instances of olddomain.com.np to newdomain.com.np in your database.
* Case Sensitivity: Linux servers are case-sensitive, unlike some local development environments. Ensure all file and folder names match their references exactly.
3. Payment Gateway Issues (Khalti, eSewa, Bank Transfer)
* Incorrect API Keys/Merchant IDs: Verify that the Khalti and eSewa API keys and merchant IDs configured in your WooCommerce or custom payment gateway settings are correct for your live environment. Test them thoroughly. * Callback/Webhook URLs: Ensure the callback URLs registered with Khalti and eSewa point to your new domain. If these are incorrect, payment confirmations won't be received, leading to failed orders. * Firewall/IP Restrictions: Sometimes, payment gateways restrict access based on IP addresses. If your new hosting server has a different IP, you might need to update this with Khalti or eSewa support. Hosting Nepal's support team can assist with providing your server's IP. * SSL Certificate: Payment gateways require a valid SSL certificate. Ensure HTTPS is enforced and your SSL is correctly installed and active on the new server.
4. Email Not Working
* DNS MX Records: Check your domain's MX (Mail Exchanger) records. If you moved to a new host and want to use their email services, your MX records must point to the new host's mail servers. If you use a third-party email service (like Google Workspace or Zoho Mail), ensure the MX records are still correctly pointing to them. * Email Account Re-creation: If you manually migrated, you might need to re-create email accounts and import old emails (if necessary) on the new server.
Conclusion
Migrating an e-commerce website with integrated payment gateways like Khalti, eSewa, and bank transfers requires a structured approach to prevent downtime and ensure business continuity. By following this comprehensive checklist, from meticulous pre-migration planning and robust backups to strategic cPanel transfers and diligent post-migration verification, Nepali website owners can achieve a seamless transition. Remember to leverage the expertise of your hosting provider, such as Hosting Nepal, which offers dedicated support for migrations, ensuring your online store remains operational and profitable throughout the process. A well-executed migration sets the foundation for improved performance, security, and scalability for your growing online business in Nepal.