Do you take over a system built by another developer?
Yes — this is the most common scenario JBKR Web handles: the original developer disappeared, left the company or shut down, and the system was left with nobody who understands it. The company takes over applications in PHP, Java, .NET/C#, Classic ASP, jQuery and VB, with no need for contact with the original author.
The first step is recovering technical control: gathering access (hosting, database, source code, domain), taking a full backup and mapping what the system does. Only then do fixes and improvements begin — prioritized by urgency together with the client.
Working on someone else's code demands discipline: small changes, tested in a separate environment before going live, with a record of everything modified. That is how an "untouchable" system starts evolving safely again.
My system has no documentation. Can it be changed without breaking?
Yes — missing documentation is the rule, not the exception, in legacy systems. JBKR Web rebuilds the understanding by reading the source code and the database: which screens exist, which routines run automatically, which external services the system depends on.
The fear of touching it and breaking it is legitimate, and the answer is process: every change goes through a test environment that mirrors production, with a backup taken before each release. If anything misbehaves, the previous version is restored immediately.
As a by-product of maintenance, the system gains the documentation it never had — a map of modules, credentials and critical routines — so the company stops being hostage to a single person's memory.
How much does it cost to maintain an old PHP, Java or .NET system?
For one-off requests — fixing a bug, adjusting a report, updating an integration — the On-Demand Plan applies, from R$250/hour, with an estimate presented before the work starts.
For production systems that need ongoing care, the monthly plans are usually cheaper than isolated support calls: Care Plan from R$1,125/month and Expert Plan from R$2,050/month, with included hours, priority support and continuity — the person handling each request already knows the system, so understanding is never rebuilt from zero.
Is it better to migrate gradually or rewrite the system from scratch?
In most cases, migrate gradually. A full rewrite is expensive, takes longer than estimated and carries a hidden risk: the old system embodies years of undocumented business rules, and the new one tends to "forget" cases the old one handled.
JBKR Web's approach is stabilize first — fix bugs, update the environment, guarantee backups — then modernize in parts: a new module in current technology runs alongside the legacy until it replaces it, without stopping the operation.
A complete rewrite is recommended only when the technology makes continuity unviable — for example, when the platform no longer runs on current servers and there is no upgrade path. Even then, the migration is planned in phases, with the old system serving as a living specification.
Frequently asked questions
Do you maintain systems built by another developer?
Yes — it has been one of JBKR Web's specialties since 2006. The process starts with an analysis of the source code, database and hosting environment. The company documents what it finds, fixes the urgent problems, and takes over ongoing evolution of the system, even with no contact with the original author.
The developer of my system disappeared. What should I do?
Gather whatever you have: hosting, database, source code and domain access. JBKR Web runs a diagnostic with the available material — even if incomplete — recovers technical control with a full backup and documented credentials, and the system returns to normal maintenance, with fixes and improvements.
How much does it cost to maintain an old PHP system?
One-off requests are handled under the On-Demand Plan from R$250/hour, with an estimate before the work starts. Continuous maintenance uses the monthly plans: Care Plan from R$1,125/month and Expert Plan from R$2,050/month, with included hours and priority support. For production systems, a monthly plan usually pays off.
Is it better to rewrite from scratch or migrate gradually?
In most cases, gradual migration. A full rewrite is expensive, slow and risky, because the old system carries years of undocumented business rules. JBKR Web stabilizes the current system and modernizes it module by module, keeping it running. A full rewrite is only advised when the technology makes continuity unviable.
My system has no documentation at all. Is that a problem?
It is not a blocker — it is the most common situation. JBKR Web rebuilds the understanding by reading the source code and the database, and produces the essential documentation during maintenance itself: module map, credentials, dependencies and critical routines. The company stops depending on one person's memory.
