Delphi migration that keeps your business rules
The Delphi app is stuck on an old version, and the people who built it have moved on. CQTecnologia upgrades Delphi and C++Builder systems and keeps the business rules in them working.
You get a written scope and estimate before any work starts.
Multi-tenant SaaS only when that is the goal.
What the upgrade covers
For Delphi and C++Builder, from Delphi 5 to current versions.
- Delphi and C++Builder systems moved from Delphi 5 up to current versions.Project, package and build upgrades step by step, so the application compiles on a current toolchain.
- Unicode: from ANSI strings to Unicode text.Strings, file I/O, data access and DLL boundaries reviewed wherever ANSI and Unicode meet.
- Retired components: the libraries that are no longer supported.Unsupported third-party components replaced with maintained equivalents, or rewritten.
- Client-server to multi-tenant SaaS, when that is the goal.SQL and business logic separated from the forms, so one system can serve many clients through an API.
- Business rules kept: the system keeps doing what the business relies on.Rules checked against real inputs and outputs before and after every change.
- Multithreading and performance tuning.Freezes, slow queries and thread contention found and fixed.
How it goes
The work goes after the cause of a problem rather than its symptom, and is checked along the way.
Discovery
We listen, ask what matters and write the scope and estimate. Work and billing start only when you agree.
Prototype
A working first version early, so you can see the idea run and change course while it is cheap.
Delivery
The finished software, checked against the scope and reviewed, with a written record of what changed and why.
Support
We stay on for fixes and next versions, so the software keeps up with your business.
Questions that come up
Old Delphi code feels risky to touch. Where does it start?
With a written scope and estimate, before any work or billing starts. Changes are then checked against the source and reviewed as the work goes.
The people who knew the code have left. Is that a problem?
It is one of the situations this service is for. The first step is the same: describe the system in a few lines by email.
My project is small. Is it worth asking?
A small fix or a code review is a good place to start. Describe it in a few lines.
How much does it cost?
There is no public price list. You get a scope and estimate in writing first, and work and billing start only once you agree.
One of several services
Delphi migration sits next to our custom software, consulting and AI work.
Got a problem to solve, or something you want built?
Describe it in a few lines. A small fix or a code review is a good place to start.
You get a written scope and estimate before any work starts.