Moving a website from Plesk to mybox involves more than transferring files and databases. The hosting environment, management interface, and resource model are different, so some features may be located in different places or work in a different way after the migration.
This article explains the main changes you can expect when moving from a Plesk-based hosting account to mybox.
Table of Contents
The hosting model is different
Many Plesk hosting environments are built around predefined plans that bundle storage, processing power, memory, and additional features into a single package. When one of those resources reaches its limit, the typical solution is to switch to a larger plan.
mybox uses Modular Web Hosting. Instead of replacing your entire hosting package, resources can be adjusted independently through Add-ons and Boost Packs.
Traditional hosting vs. Modular Web Hosting
| Traditional hosting | Modular Web Hosting |
|---|---|
| Resources are grouped into predefined plans. | Resources can be adjusted independently. |
| Upgrading usually means changing to another plan. | Only the required resources need to be increased. |
| Features and limits are tied to the selected package. | Hosting environments evolve through Add-ons and the elastic scaling option. |
The practical difference is that your hosting environment can adapt gradually as your website grows.
The control panel is different
mybox does not use Plesk. Website settings, databases, email accounts, and hosting resources are managed through the mybox panel.
After the migration, some features may be located in different sections. For example:
- Website management is handled from the Websites section.
- Resource upgrades are managed through Add-ons and Boost Packs.
- Email accounts and webmail settings are managed separately.
- Databases can be created and managed from the database section of the panel.
Although the interface is different, the technologies behind your website remain the same. Websites still depend on files, databases, DNS records, and email services.
Resource limits are managed differently
Plesk hosting plans often present limits as part of a package. In mybox, resources such as CPU, memory, storage, and the number of websites are displayed separately.
For example, One Box starts with:
- 1 GB of RAM.
- 1 GHz of CPU power.
- 5 GB of storage.
- Support for one website.
These resources can be expanded independently through Add-ons without changing to a different hosting plan.
Some familiar tools may work differently
Plesk includes many management tools directly within its interface. After moving to mybox, the way you perform certain tasks may change.
Depending on your website, you may still use:
- FTP or SFTP to upload files.
- PHP applications such as WordPress.
- MySQL or MariaDB databases.
- DNS records to connect domains and email services.
The website itself usually does not need to be modified simply because it has been moved to a different control panel.
Email settings may need to be updated
If your email service is migrated together with your website, devices and email applications may require new settings.
You may need to update:
- Incoming and outgoing mail server settings.
- Saved passwords in email applications.
- DNS records related to email delivery.
Webmail access on mybox is available at mail.mybox.com. This article explains what SMTP settings you should use in your email client if you migrated to mybox.
DNS changes can take time
If the migration includes changes to nameservers or DNS records, the new configuration may not become visible immediately across the internet.
During this period, some visitors may still reach the previous hosting environment while others are directed to mybox. This behavior is expected and usually resolves automatically after DNS propagation finishes.
What to expect after the migration
Most websites continue to work normally after being moved. However, you may notice differences in the hosting panel, resource management, and the way upgrades are handled.
If something behaves differently than it did in Plesk, this does not necessarily indicate a problem. In many cases, the difference comes from the transition from a traditional hosting model to Modular Web Hosting.