How Do I Review and Take Over PHP Code Inherited From Another Provider?

By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.

Profiles: GitHub · LinkedIn.

Published: · Last technical review:

Yes: I maintain, fix, and evolve PHP and MySQL applications that your company already has running, even if built by another provider. Maintenance starts from €60/month + VAT* (security, backups, and bug fixes), with new features quoted separately after reviewing your case and agreeing on scope in writing.

Criteria: separate taking on a need from taking on everything

If your application comes from another provider, you can explain what it does and what you need resolved right now. You do not need to justify why you are looking for another developer or turn the inquiry into an assessment of previous work. I suggest starting from observable tasks, described problems, and features you want to retain. The priority is to agree on what review you are requesting, not to pass judgement on code I have not yet seen.

On my website, I state that I maintain existing PHP applications whether I developed them myself or they are already running in your company. Maintenance includes security updates, backups, and bug fixes. New features are quoted separately. This allows you to inquire about an inherited application; it does not establish automatic acceptance of any code or previous contractual terms.

What scope I would propose reviewing first

I would suggest identifying the tool, the task most relevant to your inquiry, and the behaviour you want to maintain or change. We would then need to agree on what information allows us to assess that scope. If deliverables documentation exists, you can describe what it contains without sending secrets. If you do not know who holds the code or hosting, I would mark it as pending information, not as a reason to invent an answer.

Proposed question Why I want to clarify it
What does the application do for your business? Defining the tool we are evaluating
What problem or change prompts the inquiry? Separating current needs from subsequent enhancements
What functionality do you want to preserve? Preparing a reviewable benchmark
What documentation can you identify? Knowing what agreements should be consulted
Who can authorise the review? Avoiding confusing application usage with permission to intervene

This table is a discussion guide, not an audit carried out.

I would not ask you to gather everything before writing to me. I would, however, suggest distinguishing the information you know from what you need to confirm with your company or provider. A clear account of what is missing is more useful for preparing scope than a list of assumed answers. I do not take for granted that switching developers implies moving hosting, rebuilding the application, or replacing every component.

My own proof: continuity for existing applications

My published offering covers maintaining, fixing, and evolving operational PHP and MySQL. I also outline a process of written diagnosis, scope and quote before development, direct contact, and functional progress you can test. Those are the facts I can currently provide about my service; I do not attribute quality, technical debt, or modification possibilities to your application without a review.

Maintenance has a starting price from €60/month + VAT*, without that benchmark setting a fixed quote for your case. Taking over third-party inherited code requires first reviewing your application and agreeing on its scope. I do not present a project of my own as an external client commission, nor do I invent results from applications I have taken over. The available evidence here is my published offering and terms.

When you should NOT change everything from the outset

Faced with an application inherited from another provider, it is advisable to first consider a scoped review to stabilise what is already working before proposing a complete rebuild. The first alternative preserves the starting point as an object of study; the second requires defining what you want to build and what would cease to be used. I would not choose one simply because the code belongs to someone else, nor would I present rebuilding as a universal requirement.

If your request is to add new capabilities, it is best to separate it from the maintenance you need for what already functions. If it is to clarify a bug, I would suggest describing expected and observed behaviour. Changing providers does not erase that distinction. The offering publishes new features separately, and the work agreement should recognise them as such before turning expectations into deliverables.

Nor is it advisable to treat an inquiry as authorisation to access systems or data. First, we need to specify what review is appropriate and who can authorise it. I do not suggest providing credentials in the initial message or intervening in production to find out the state of the application. Access and interventions must be agreed upon subsequently; I receive credentials by email as outlined in the contract, and you must rotate them once the work is completed.

How I would propose organising the transition

As preparation, I would suggest a list of what you need to keep, what you want to fix, and what you wish to evaluate later. I would not call it a complete technical inventory if it has not been reviewed. In that list, I would include questions about documentation, authorisations, and existing agreements. Its function would be to clarify the starting point, not to attribute responsibilities to me that we have not yet defined or replace previous terms without examining them.

In my process, deliverables, deadlines, and budget are set out in writing before development. For an inherited application, I would suggest applying that same clarity to the review and any subsequent actions, without taking them as accepted in advance. If a conclusion depends on missing information, I would keep it visible. I would not promise to take on any code or fix any problem for the starting price.

What to prepare without turning it into a report

To prepare your initial inquiry, note down what your PHP/MySQL application does today, who manages hosting, what you need covered under maintenance, and what new features or deliverables you would like evaluated separately. I suggest bringing those answers as discussion points. They are not a certificate of your software's health or an acceptance that you must contract every change that emerges while describing it.

What I would not deduce from switching providers

I would not assume you want to modify contracts, licences, or hosting terms merely by asking for a review. I suggest identifying what agreements exist and which you need to clarify, without asserting that an absent document grants additional permissions. I would also separate information that belongs to you from what you cannot share. These are questions to prepare the transition, not legal conclusions or terms I have already accepted. The new scope must explain the work you want assessed, not silently replace all previous agreements.

Transition checklist before touching production

For an orderly transition, I suggest identifying the following elements without asking for secrets in the first message. It is an inventory to be agreed upon, not an included intervention or a review already conducted. You send credentials by email as outlined in the contract, and you must rotate them once the work is completed. The required technical inventory is specified for each transition.

With that information, I would outline what is needed to review the code without disrupting production. If the repository is unavailable or the schema is undocumented, I would leave it as an open question: I would not invent a structure or promise to resolve the transition merely by changing points of contact.

Frequently asked questions

Does the application have to be built by you?

No. On my website, I explain that I maintain and evolve existing PHP applications even if I did not build them myself. Before finalising the work, I need to assess your need and agree on scope. That availability does not mean automatically accepting any codebase, all prior terms, or new features within the maintenance retainer.

What scope do I review first?

I suggest starting with the tool, the problem or change prompting your inquiry, and the behaviour you need to preserve. We would then agree on what information and authorisations the review requires. Deliverables, budget, and timeframe are set out in writing before development. I do not consider a full audit or application replacement included simply by switching developers.

PHP maintenance and evolution

PHP maintenance and evolution

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

Related articles

* Indicative starting prices, subject to conditions and change. VAT not included: charged separately at the applicable rate. The final amount is set in a written quote after reviewing your project and is binding only once accepted by both parties. Quotes are valid for 30 days. Full terms: General terms.