A restore-tested backup
The quote should state who takes the backup, where it is stored and when a restore is tested.
There is no honest single price for a Joomla migration. Two sites on the same version can need very different work. A free audit replaces guesswork with a clear scope, assumptions and a fixed quote before work begins.
No fake from-price. No surprise scope. The quote lists what is included, what is excluded and what is still an assumption.
The version is only one input. These are the practical cost drivers we check before quoting.
| Factor | Why it affects the quote |
|---|---|
| Current version | Joomla 3 and Joomla 4 follow different upgrade paths and compatibility rules. A long-overdue site may need a more staged approach. |
| Extensions | Maintained extensions are simpler to carry over. Abandoned or heavily customised ones need replacement, reconfiguration or a rebuild. |
| Template | A responsive template may be adapted; an old table-based or heavily customised template usually needs rebuilding. |
| Content and media | Thousands of articles, large media libraries and multilingual content take longer to map and verify. |
| E-commerce | A VirtueMart or HikaShop store adds products, orders, tax, shipping, gateways and checkout testing. |
| Custom code | Custom components, modules or plugins need to be understood and either ported or replaced. |
| URLs and SEO | A redirect map, metadata review and internal-link checks protect search equity; skipping them is a false saving. |
| Hosting and PHP | The current server stack may need changes before the new release can run safely. |
| Timeline | Compressed schedules require more parallel work and carry more risk; we quote that explicitly rather than hide it. |
We do not publish a fake “from” price. The audit establishes the facts, and the quote turns them into fixed milestones.
A cheap headline number is not useful if it leaves out the work that protects your content and search traffic.
The quote should state who takes the backup, where it is stored and when a restore is tested.
The new site should be built and tested away from the live site before cutover.
Articles, categories, users, media and important URLs are accounted for—not just “content migration”.
Each critical extension is either carried over, replaced or explicitly scoped as custom work.
Forms, search, e-commerce, mobile and redirects need named checks, not a vague “test before launch”.
The handover should state what happens if a defect appears after launch.
“They are very knowledgeable about Joomla!® and were very helpful throughout the project, even though we were not 100% sure about what we wanted to do.”
Straight answers before you compare quotes.
There is no honest single figure. A small brochure site and a multi-language store require different work. We provide a fixed-scope quote after the free audit, with assumptions and exclusions listed.
Yes. The public audit checks the site from outside and gives you a written starting point. Any confirmed migration scope and quote follow a short review.
We can discuss the likely complexity band from a short brief, but we do not turn that into a fake fixed price. The audit and a look at the extension list are what make a real quote possible.
A restore-tested backup, staging build, content and URL map, extension replacement plan, test plan, redirect map, launch support and the agreed post-launch fix window. The SOW says exactly what is in and out of scope.
A migration that skips backups, staging or URL mapping can cost more to repair than it saves. Compare scope, testing and what happens after launch—not just the headline number.
Pick the next question that matches your situation.
Run the free audit, send the extension list and tell us what matters commercially. We will quote the work—not a guess.