ScalaHosting and Joomla launched a migration campaign on September 28, 2026, that lets eligible Joomla site owners test a copied site for three days before switching providers. If ScalaHosting cannot make the migrated site load faster under the campaign’s stated measurement process, it says it will pay the customer $100.
What Happened
Eligible customers can request a free migration of an existing live Joomla site to a parallel ScalaHosting environment. The campaign says no credit card is required for the three-day test and the original site stays online during the evaluation.
ScalaHosting records a baseline before migration and then measures the optimized copy after migration. According to the published terms, both tests use the same measurement tool and test location, with results averaged across multiple runs. If the optimized site is still slower, an eligible customer can submit one claim within seven days.
The offer applies to ScalaHosting cloud or managed VPS plans purchased through the campaign site. The terms exclude changes made after migration and performance controlled by third-party services.
Why It Matters
Hosting speed guarantees are often too vague to evaluate. This campaign is more useful because it describes a comparison method, a testing window, a claim period, and major exclusions. The parallel-copy approach also reduces migration risk because a customer can inspect the result before redirecting production traffic.
The guarantee still measures one dimension of hosting. Full page-load time can change with caching, extensions, templates, database condition, geographic distance, and third-party scripts. Reliability, support quality, security operations, and renewal pricing remain separate purchase decisions.
What the Company Says
ScalaHosting says its team performs the migration and optimization, and that the customer receives $100 if the new copy does not beat the recorded baseline under the campaign rules. The campaign page listed managed cloud hosting from $14.95 per month when checked on October 5, 2026, while also stating there is no setup fee or required long-term contract.
The Joomla-hosted campaign page discloses that the products and services are provided, supported, and warranted by ScalaHosting—not Joomla or Open Source Matters—and that the Joomla trademark is used under license.
HostingReviewLab Context
The offer is most relevant to owners of established Joomla sites who want evidence before changing hosts. A clean test should preserve the application, database, extensions, PHP version, caching settings, and test geography closely enough that the hosting environment is the main variable.
Our guides to VPS hosting, managed versus unmanaged VPS hosting, and evaluating hosting speed tests explain the broader tradeoffs and how to interpret a benchmark.
What We Haven’t Independently Verified
HostingReviewLab has not submitted a Joomla site to the campaign, reproduced the before-and-after test, validated a $100 claim, or independently compared ScalaHosting’s infrastructure with the customer’s previous host. The campaign process, starting price, and eligibility rules are provider-published terms.
What Customers Should Know
- Use a representative site and confirm that the migrated copy includes the same extensions, content, PHP version, and third-party dependencies.
- Save the baseline, post-migration results, timestamps, test location, and configuration details.
- Read the one-claim-per-client rule, seven-day deadline, and exclusions before purchasing.
- Verify the current localized price, renewal terms, resource allocation, backup policy, and support scope at checkout.
- Keep the original site and a current backup until DNS changes have been validated and rollback is possible.
Event date: September 28, 2026. Source checked: October 5, 2026. Price checked: October 5, 2026. Updated: October 6, 2026. Verification status: Corroborated.
Make the before-and-after comparison interpretable
Ask for the tested URLs, dates, locations, cache state, software versions and metric before interpreting a speed claim. Keep the same page content and comparable conditions where possible, and record any optimization performed during the move. A result following both migration and application changes describes the combined intervention. It cannot isolate the hosting contribution without additional evidence. Review the campaign's own claim procedure separately.