Start with the platform you have
A version number alone does not define an upgrade. Custom code, packages, content structure and integrations determine the work. JP Codex reviews those dependencies with your team before proposing a delivery scope, including Umbraco 13 to 17 upgrades where appropriate.
Make compatibility decisions early
The assessment identifies packages that can be upgraded, dependencies that need replacement and custom functionality that needs adaptation. Content, database and integration changes belong in the same plan as the CMS and runtime changes.
Plan testing and deployment together
Agree acceptance criteria for editor workflows, public pages and business integrations. Prepare representative test environments, migration rehearsals and deployment steps before release. Rollback and data recovery options depend on the application and database changes involved.
What an engagement can cover
Support can include pre-upgrade analysis, estimation, implementation, package replacement, integration changes, content and database migration, Azure configuration, CI/CD and QA support. Scope is agreed around the platform and your delivery team; completion dates and downtime requirements need assessment.
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.
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