Django 4.2 LTS
Security support ended: April 2026
New Django vulnerabilities are no longer patched on 4.2. Django 5.2 LTS is supported until April 2028, so it is the natural target.
For startups and SMBs: we upgrade aging Django, Python and cloud infrastructure before it falls out of support, without a risky rewrite. Tests go in first, then the upgrade, then a cutover you can roll back, with slow pages and cloud cost fixed along the way.
An example upgrade, before and after
Critical flows covered, CI blocks regressions
Approved by the lead engineer. Rollback rehearsed and on standby.
Nothing reaches production without a person signing offDeadlines
Most support windows for the stack Django products run on closed in 2026. Past these dates, security fixes stop, and on AWS some of them start costing extra.
All 5 of these deadlines have already passed.
Support endedEnds soon afterSafe target
Security support ended: April 2026
New Django vulnerabilities are no longer patched on 4.2. Django 5.2 LTS is supported until April 2028, so it is the natural target.
End of life: April 2026
Frontends, build tooling and server code on Node.js 20 now run on a release line that no longer gets upstream security fixes.
End of support: June 2026
Servers and machine images still on Amazon Linux 2 no longer receive security updates and need moving to a supported operating system.
End of standard support: July 2026
Instances still on MySQL 8.0 move to paid RDS Extended Support. Upgrading to a supported engine version avoids that charge.
End of life: October 2026
Python 3.9 already ended in October 2025. Python 3.11 reaches end of life in October 2027, so a one-step upgrade buys only a year.
Moving off a platform you have outgrown follows the same path: tests first, a staged move, and a cutover you can roll back.
Cloud Migration & DevOps →Not sure which versions you run? Paste your requirements.txt, package.json or Dockerfile into our free end-of-life checker. It runs in your browser and shows every date. Planning a Django upgrade? The Django upgrade checker lists what breaks in your code between your version and the target.
Services
From a single Django version bump to moving a whole product off an aging platform, with the test coverage that makes each step safe.
Move Django 4.2 or older to 5.2 LTS and Python to a supported release, one version step at a time, fixing deprecations as we go.
Most aging codebases have thin tests. We add tests around the paths that matter before touching versions, so every step is checked.
Move servers off Amazon Linux 2, runtimes off Node.js 20, and databases onto supported engine versions, testing your app on each new platform first.
Move off an old database or engine version with rehearsed migrations and data checks before and after, so you can prove nothing was lost.
Upgrading a Django codebase specifically? See Django Modernization. Changing clouds or leaving a platform? See Cloud Migration & DevOps. Planning AI next? Data stuck behind an unsupported database or old framework is the usual blocker, so modernizing first gives AI Agents in Production something solid to build on.
Cost & speed
An upgrade already touches every layer, so we fix performance and cloud spend in the same pass instead of selling it as a separate project.
We profile the slowest endpoints and fix the usual causes: N+1 queries, missing indexes, and work that should be cached.
We measure LCP, INP and CLS on your real pages and fix what drags them down: heavy assets, blocking scripts and slow server responses.
We find oversized instances, forgotten environments, and orphaned volumes and snapshots, then resize or remove them.
For teams already running AI features: caching repeated requests, routing simple calls to smaller models, and tracking cost per request.
Included in every Upgrade Assessment, not sold as a separate project.
Upgrade or rebuild
The honest version of the trade-off. Most systems need the smallest change that removes the risk, not a rewrite.
Quick check · 0/3
Answer a question to see which option fits.
How we upgrade
The order of work is the safety: tests first, then the upgrade, then a cutover you can roll back.
We check every framework, runtime, package and service against its end-of-life date, and map where the tests are thin.
We add tests around the critical paths and wire them into CI, so each upgrade step is checked before it ships.
We move one version step at a time, fixing deprecations and replacing dead packages, instead of one big-bang jump.
We rehearse the data migration and cutover in staging, ship with a tested rollback, and watch production closely afterward.
By the time traffic moves, every step has been tested, staged and rehearsed, and the way back is already proven.
Your first step
A fixed-scope first step that shows what is out of support, what the upgrade will take, and where your cloud bill and slow pages can be fixed, before you commit to the work.
A clear picture of what you run, what is past or near end of life, and the safest order to fix it.
Upgrade in stages behind a test safety net, then switch over with a plan you have already rehearsed.
Stay current so you never face a cliff-edge upgrade again.
Stack
The systems we most often upgrade and migrate, and the tooling we use to keep every step tested.
What your product runs on
Where it keeps its data
What keeps every step tested
Selected work
Django platforms we have built for clients and for ourselves.
View full portfolio → Our open-source Django projects →Self-hosted CRM platform for startups and SMBs, combining CRM workflows, invoicing, support, multi-tenant architecture, and full-stack product delivery.
Read case study ↗Fire safety compliance platform for Australian building owners with automated service regime calculations, asset tracking, and document workflows.
Read case study ↗Loan advisor portal with affiliate network management, dynamic dashboards, and workflow support for financial consultants.
Read case study ↗FAQ
Straight answers to what founders and CTOs ask us before an upgrade or migration.
Ask it on a free 30-minute call. We reply within one working day.
Ask us →Legacy modernization is upgrading the frameworks, runtimes, databases and infrastructure under an existing product so it stays supported, secure and fast, without rebuilding it from scratch. In practice that means version upgrades, dependency cleanup, database and platform migrations, and fixing performance and cloud cost along the way, usually in stages so the product keeps running throughout.
Not for long. Django 4.2 LTS stopped receiving security fixes in April 2026 and Python 3.10 reached end of life in October 2026, so any vulnerability found after those dates stays open in your stack. The app keeps running, but the packages you depend on gradually drop support for old releases, which makes every later upgrade harder. Plan the move now: Django 5.2 LTS is supported until April 2028.
Plan the move now. Amazon Linux 2 reached end of support in June 2026, and Amazon RDS for MySQL 8.0 reached the end of standard support in July 2026, after which instances still on it move to paid Extended Support. We upgrade the operating system, machine images and database engine versions in stages, testing your application on the new platform before switching traffic.
It is a fixed-scope first step with three parts. We audit every framework, runtime and dependency against its end-of-life date, lay out an upgrade path that calls out where tests are missing and where the risks sit, and review your cloud bill and slowest pages for cost and speed fixes. You come away with a written plan and a fixed estimate for the upgrade, so you can decide what to do and in what order before committing to the work.
By keeping each change small and reversible. Tests go in first so regressions are caught before release, the upgrade ships in stages rather than as one big switch, and the data migration and cutover are rehearsed in staging with a tested rollback plan. Most steps ship like any normal release. Where a cutover needs a maintenance window, we schedule it for your quietest hours and keep it as short as possible.
Yes. The upgrade already touches every layer, so it is the right moment, and the Upgrade Assessment includes a cost and speed review. We profile slow pages and queries (N+1 queries, missing indexes, missing caching), check Core Web Vitals, and look for oversized or idle cloud resources. For teams already running AI features, we also cut LLM and inference cost with caching and model routing.
Yes, for the mechanical work. AI-assisted tooling speeds up syntax changes, deprecation fixes and first drafts of tests, and an engineer reviews every change. Our engineers own the parts where upgrades actually fail: test coverage, data migration and the cutover itself. AI makes the repetitive work faster; it does not decide what is safe to ship.
It depends on scope: how many versions you are behind, how many third-party packages need replacing, and how much test coverage exists today. A small app one LTS release behind is a very different job from a large codebase several versions back with thin tests. The Upgrade Assessment answers this for your system, and you get a fixed estimate for the upgrade after it.
Yes. You own all source code, tests, infrastructure configuration and documentation we produce. Everything is committed to your repositories as we work, with no lock-in, so you can run, extend or bring the work in-house at any time.
We reply within one working day