Umbraco upgrade assessment

When an assessment is useful

You may have a target version but no dependable estimate, inherited a platform with unfamiliar packages, or need an independent view before committing to delivery. An assessment gives agencies and platform owners a way to resolve uncertainty before scheduling implementation.

What we review

The review is shaped around your platform and the decisions you need to make. Agree the depth and access first, then examine the application and its release path together.

Current Umbraco and .NET versions, custom code and back-office extensions
Package compatibility, replacement candidates and external integrations
Content, media and database migration considerations
Azure environments, configuration, CI/CD and release dependencies
Acceptance scenarios, investigation risks and recovery requirements

What the assessment can give your team

Outputs are agreed before work starts. A useful assessment makes both findings and uncertainty visible, with enough context for your team to decide what happens next.

A compatibility register showing supported, unresolved and replacement items
A prioritised risk and decision list with evidence still needed
A proposed scope with dependencies, assumptions and exclusions
An implementation estimate with investigations identified separately
An outline of testing, migration, deployment and handover work

How we get started

Share your current version, the planned change and the constraint that matters most. An initial conversation establishes fit and the access needed for a scoped review. Source, package information, environment details and a walkthrough of key workflows may be needed. Credentials should be exchanged through an agreed secure channel.

From findings to delivery

Your team can use the findings to plan implementation, ask JP Codex to deliver a defined scope, or bring senior engineering support into the team. Scope, availability and commercial terms are agreed for each engagement.

Before you enquire

Can you help with a site you did not build?

Yes. An initial review establishes how the existing application works, which dependencies matter and what access is available. The proposed scope follows that review, whether the next step is an assessment, implementation or embedded support.

What determines the cost and timing of an upgrade?

The starting version, custom code, packages, integrations, data migration and release requirements all affect the work. JP Codex discusses scope, assumptions and unresolved investigations before agreeing an estimate. A version number alone is not enough for a reliable quote.

Will we work directly with the engineer doing the work?

JP Codex provides hands-on engineering and consulting. Technical discussions connect directly to the work being assessed or implemented.

Can you work alongside our agency or internal developers?

Yes. Deliver covers a defined project, Advise covers reviews and recommendations, and Embed provides remote senior engineering support within a delivery team. Responsibilities, access, communication and availability are discussed for each engagement.

What do you need from us to start?

Begin with your current platform, the problem or planned change, known constraints and your preferred engagement. Repository and environment access can be arranged after the review scope and access requirements are agreed. Do not send credentials through the enquiry form.

What happens after implementation?

Testing, release preparation, deployment support, documentation and handover can be included in the agreed scope. Any follow-on support, responsibilities and availability are discussed explicitly rather than assumed to be part of every project.

Useful next steps

Continue exploring

Consulting services / Engineering guides

Discuss your platform

Share your current platform, the change you need and your delivery constraints. Scope and engagement can be discussed around your team.

Discuss an Umbraco Project