Upgrading your service plan without losing data

Upgrading your hosting service plan is one of those tasks that many website managers put off until the last moment, because they worry about data loss, prolonged downtime, and technical hassles. But if you know exactly when to upgrade, how costs are calculated, and what steps to follow, this can be done in less than an hour without losing even a minute of data. In this article, we will cover everything about upgrading your plan for your web hosting service; from calculating pro-rata costs to scheduling changes and secure data migration methods.

When Do You Really Need to Upgrade Your Plan?

Before taking any action, you need to make sure that your problem will be solved by upgrading the plan, and not by optimizing code or cleaning up the database. Here are three main signs that it's time to upgrade:

• Resource usage is nearing its limit: If CPU or RAM usage is consistently above 80% and reaches 100% during peak hours, an upgrade is necessary.
• Response time has increased: If your site's TTFB (Time To First Byte) has exceeded 1 second and this condition is persistent, your current service cannot handle the traffic.
• Frequent 508 or 503 errors: These errors mean the server cannot process requests, usually due to resource limitations.

A common mistake is that users upgrade their plan immediately upon seeing a temporary error. Before upgrading, be sure to review usage statistics over a period of at least 7 days. If you've only had one busy day, it might be better to enable caching or optimize images instead of upgrading.

Calculating Pro-Rata Costs; How Much Will You Pay?

Most hosting companies, including ServerNet, calculate the cost of a plan upgrade on a pro-rata basis. This means you only pay the difference between the price of the new plan and the old one for the remainder of your current billing period.

Pro-Rata Cost Formula

Pro-rata cost = (New plan price - Old plan price) × (Remaining days ÷ 30)

Real example: Suppose your current plan costs 200,000 Toman per month and you have 20 days left in your billing period. If you upgrade to a plan priced at 400,000 Toman:

(400,000 - 200,000) × (20 ÷ 30) = 200,000 × 0.66 = 133,333 Toman

This amount is charged as a lump sum, and the new billing period starts from the upgrade date. That is, if 20 days have passed from the previous period, the new period is calculated as a full 30 days from the upgrade day.

Important Note About Annual Billing Periods

If your service is billed annually, the pro-rata calculation is based on the remaining days in the year. In this case, the formula is as follows:

Pro-rata cost = (New plan annual price - Old plan annual price) × (Remaining days ÷ 365)

A common mistake is that users think upgrading mid-cycle will charge them the full amount of the new period. This is a misconception; you only pay the difference on a pro-rata basis.

When Will the Upgrade Take Effect; Is Downtime Unavoidable?

The short answer: No. Depending on the type of upgrade, you may experience no downtime at all, or only a few minutes of downtime.

Resource Upgrade Without Physical Migration

If your upgrade only involves increasing RAM or CPU and your server remains on the same physical machine, it is usually done without downtime. In this case, changes are applied via Hot-Plug, and your website will not be inaccessible for even a moment. This scenario is more common with VPS and cloud servers.

Plan Upgrade Involving Migration to a New Server

If the upgrade requires moving to a different physical machine (e.g., from shared hosting to a VPS), a short downtime is unavoidable. Typically, this downtime lasts between 5 and 15 minutes and involves the following steps:

1. Creating a full backup of files and the database
2. Transferring data to the new server
3. Changing DNS or IP (if necessary)
4. Final testing and announcing that the service is active

The best time to do this is during your website's low-traffic hours. If your site has an Iranian audience, the period between 2 AM and 5 AM is usually the best time.

Steps to Upgrade Your Plan Without Losing Data

Now that you are familiar with the costs and timing, let's go through the practical steps one by one.

Step One: Full Backup

Before taking any action, create a complete backup. This should include the following:

• Website files (including public_html and all subdirectories)
• MySQL database (using phpMyAdmin or the mysqldump command)
• Cron Job settings and server emails

Sample command for backing up the database:

mysqldump -u username -p database_name > backup_$(date +%Y%m%d).sql

Be sure to download the backup to your local system, not just keep it on the same server. If the server encounters a problem, the backup on the server itself will also be lost.

Step Two: Submitting the Upgrade Request

In your user panel, open the service management section and select the plan upgrade option. This option is usually located next to your service details. After selecting the new plan, the system will automatically calculate and display the pro-rata cost.

Important note: If your website is an online store or processes online transactions, it is better to perform the upgrade during inactive hours so that if a short downtime occurs, user transactions are not affected.

Step Three: Data Migration

If the upgrade involves moving to a new server, the hosting company usually handles the migration process. However, if you need to do it yourself, follow these steps:

1. Transfer your website files to the new server using FTP or SSH.
2. Import the database on the new server.
3. Update the configuration file (such as wp-config.php in WordPress) with the new information.
4. Change the DNS to the new IP (if the IP has changed).

Sample command for transferring files with rsync:

rsync -avz --progress /path/to/source/ user@new-server:/path/to/destination/

Step Four: Testing and Final Verification

After the upgrade is applied, be sure to test the following:

• Loading the main page of the website
• Logging into the admin panel (such as wp-admin)
• Connecting to the database and running a simple query
• Sending and receiving emails (if you use email services)

Most Common Mistakes When Upgrading Your Plan

In this section, we will review several frequent mistakes that can cost you.

Mistake One: Upgrading Without Assessing the Real Need

Many users upgrade their plan as soon as their website slows down, even though the problem might be due to heavy code, unoptimized images, or insufficient caching. Before upgrading, be sure to conduct a full audit of your website.

Mistake Two: Forgetting to Take a Backup

This is the most important mistake. Even if the hosting company promises to transfer your data, you should still have a local backup. In the event of any error, this backup is your only lifeline.

Mistake Three: Upgrading During Peak Traffic Hours

If your website receives the most visits during working hours (e.g., 9 AM to 5 PM), postpone the upgrade to the evening. This minimizes the risk of losing transactions or user registrations.

Mistake Four: Not Checking Settings After the Upgrade

After the upgrade, some settings such as the maximum upload size (upload_max_filesize) or PHP memory limit (memory_limit) may revert to default values. Be sure to check these values and correct them if necessary.

Conclusion; A Smart Upgrade, Without Stress

Upgrading your service plan, if done with awareness and planning, is a simple and hassle-free process. All you need to do is follow three key points: first, make sure you really need the upgrade; second, calculate the pro-rata cost so you are not surprised; third, take a full backup before any action.

If your service is on shared hosting and you need more resources, upgrading to a VPS or cloud server can be a suitable option. Companies like ServerNet offer a variety of hosting plans and cloud servers that you can choose from based on your needs. Just remember: an upgrade is an investment, not an extra expense. If your website has grown and has real traffic, a timely plan upgrade will create a better user experience and ultimately contribute to your revenue.