A clear path from an old Umbraco version.

The starting version is only part of the scope. Custom code, packages, content models, integrations and testing requirements all affect the work. We review the implementation first, then provide a scoped estimate with assumptions and options. A version number alone is not enough for a reliable quote.

Often, yes. An upgrade does not automatically require a redesign. We assess what can be retained, what needs adapting and where rebuilding would be more practical. Content and media are mapped and checked through trial migrations before launch.

We plan to preserve URLs, metadata and important journeys, with redirects where addresses must change. Rehearsals, a content freeze and a recovery plan help control the launch. We agree any maintenance window in advance; zero downtime or unchanged rankings cannot be guaranteed.

Yes. We start with access to the code, environments, database and package inventory, alongside any documentation and known issues. That review establishes the migration route, technical dependencies and responsibilities before delivery begins.

We set a delivery plan after the technical assessment. The time needed depends on the work to custom editors and integrations, content migration, testing and your team’s availability for review. The plan includes milestones and a proposed launch window.