MySQL development
Your application depends on MySQL, and the version or the schema has started to hold it back. We work on the database and the application together. We moved a cabinet manufacturer's ordering system from MySQL 5.0 to MySQL 8, and designed the databases behind rental platforms in Qatar and Dubai. If you are still on 8.0, Oracle's support has changed, and this page covers what to do.
In each case the database was designed or moved alongside the application.
Migrating a very old database
The cabinet manufacturer's data moved from MySQL 5.0 to MySQL 8 as part of a rebuild on Laravel 13, with validation at every step and workflows compared against the old system in parallel.
Availability and contract schemas
The Qatar equipment platform models which machine is where, until when and at what rate, with rate cards per equipment class, reservations per unit, maintenance holds and utilisation reporting.
Reusing the core for a second business
The Dubai vehicle-rental application reused the rental-contract and billing core for the same owner, and added vehicle documents, deposits, mileage terms and fines pass-through.
From Oracle's MySQL support notice, release notes and manual.
MySQL 8.0
The final release, 8.0.46, shipped in April 2026. Oracle's notice says that from 21 April 2026 it falls under Sustaining Support, and it encourages users to move to 8.4 LTS or 9.7 LTS.
MySQL 8.4 LTS
An LTS series, which Oracle's policy gives five years of premier support and three of extended support. This is the shorter step from 8.0 for most applications.
MySQL 9.7 LTS
Released on 21 April 2026 and the newest LTS series. It is a larger jump, so we would test your application and its queries against it first.
The application decides whether an upgrade worked, not the database log.
We work on a copy of your data and schema, looking for old character sets, date values, removed features and the queries that matter most.
A database upgrade can break an application in subtle ways, such as changed defaults or reserved words. The application's own flows are the test.
Row counts alone are not enough. We compare figures the business relies on, such as balances and stock, between the old and new databases.
Timing, the order of steps and a rollback route are agreed before the live move, including what happens to any data written during the switch.
Usually as a defined piece of a larger job.
A version move can be a defined project once we have seen a copy of the schema. Where the code is old as well, it usually belongs with an application upgrade; see PHP development and our Laravel upgrade service.
Review and query work can also be charged by the hour, from $20/h in USD, invoiced in USD, GBP, EUR or INR. We are an engineering team in India with 3–5 hours of overlap with the UK and Europe; US calls by appointment.
Most of our work is delivered under NDA, so many projects cannot be named.
Equipment register, availability and reservations, rate cards, rental contracts, delivery/return tracking, invoicing and utilisation reporting for a Qatar heavy-equipment rental company. Laravel, MySQL, Next.js.
Vehicle register, bookings, rental agreements with deposits and mileage terms, handover and return checks, fines pass-through, invoicing and fleet reporting for a Dubai vehicle-rental company. Second rental platform for the same owner.
Cabinet manufacturer's ordering, dealer-portal and inventory system moved from PHP 5.6 and MySQL 5.0 to Laravel 13 on PHP 8.5 and MySQL 8, with a new Next.js front end. Eight months, workflows preserved, now live.
Mostly about versions, and about what we do not offer.
Tell us the version, the rough size of the database and the application on top of it. We will tell you what we would check first.
We reply within one business day (IST).