As part of our ongoing commitment to improving performance, reliability, and security, we have recently launched a new product line built on a completely different infrastructure. This upgrade is designed to provide faster website performance, improved stability, and compatibility with the latest web technologies.
New Infrastructure
Our new hosting environment is based on the latest versions of core technologies such as PHP and MySQL, along with enhanced server configurations and resource management systems. These improvements ensure better efficiency, stronger security, and full support for modern web applications.
Applicable for New Purchases Only
Please note that the new product line is available only for new orders. Due to the difference in system architecture, these new hosting plans cannot be combined, modified, or merged with your existing packages.
Upgrade, Downgrade, or Migration
Existing plans under our previous infrastructure cannot be upgraded or downgraded to the new plans. If you wish to move to the new platform, you would need to:
Place a new order for one of the new hosting plans.
Migrate your accounts and data from your current server to the new environment.
Cancel your existing plan once your migration has been completed successfully.
Our technical team can guide you through the migration process to ensure a smooth transition with minimal disruption to your services.
Why This Change Matters
The introduction of a separate infrastructure allows us to:
Provide improved server performance and faster load times.
Offer enhanced security measures and isolation between accounts.
Support newer PHP/MySQL versions for modern website compatibility.
Ensure better resource allocation and stability for all users.
Need Assistance?
If you have any questions or would like to learn more about how to transition to the new hosting platform, please contact our Sales Team through your Client Portal. Our team will be happy to assist you with product details, migration options, and any other inquiries.
If you are setting up an account now rather than reading about the change, Getting Started with Your Ahosting Account is the place to start.
What to check before placing the new order
The two platforms differ, so it is worth confirming a few things about your current account before ordering rather than after migrating.
Note which PHP version your sites run on, which extensions they need, and whether anything depends on a specific database version. Applications written some years ago occasionally require an older version than the new environment provides, and that is better established now than during the move.
Record the size of the account and the number of files as well. Both determine how long the migration takes, and the file count matters more than the size, since a large number of small files copies far more slowly than a few large ones.
Run both accounts in parallel
The safest sequence keeps the old account working throughout, and the ability to do that is the main reason to order before cancelling rather than the reverse.
Copy the sites to the new account and test them there while the domain still points at the old one. That way every fault is found while nothing depends on the new environment, and there is no period during which the site is unavailable.
Only after the new copy is confirmed working should the domain be pointed at it, and only after that has settled should the old plan be cancelled. Each step is reversible until the last one.
What does not move with the files
A migration copies the site and several things around it stay behind.
Scheduled tasks have to be recreated. Mail forwarders and filters do not appear in a file copy. Anything configured at the account level, such as a redirect or a protected directory, is a setting rather than a file. And any external service holding your old address, including a payment provider's callback, has to be updated separately.
Make the list from the old account before it is cancelled, since the settings are only readable while it exists.
Keep the old plan until the new one is proven
The overlap costs one billing period and it is the cheapest insurance available during a platform change.
During that period, watch the old server's logs for requests that are still arriving. Anything reaching it after the domain has moved is a system configured with a fixed address rather than the domain, and each one will stop working the day the old account is closed.
That list cannot be reconstructed afterwards, which is why the overlap is worth more than the saving from cancelling immediately.
Test the new environment before committing to it
The platforms differ, and the differences are easier to find on a copy than on the live site.
Copy one site across first, ideally the least critical one, and exercise it properly: load a page that reads from the database, submit a form, upload a file and log in. Each of those uses a different part of the environment.
Where something behaves differently, that is a question to resolve while the original is still running. Discovering it after the domain has moved converts a question into an incident.
Ask before assuming something is unavailable
A component missing from the new environment is occasionally a default rather than a policy, and a request is cheaper than redesigning around it.
That applies to a specific extension, an older interpreter version, or a limit that is lower than the one you are used to. Some are fixed by the architecture and some are a setting.
Ask with the specific requirement rather than in general terms. A request naming the extension and the application that needs it is answered directly, where a question about compatibility produces a general reply.