Taking over someone else's .NET application: a first-month plan
A week-by-week plan for your first month with an inherited .NET application: access, a clean build, backups, tests, releases and monitoring.
· 8 min readWhat owning your bespoke software involves, how to find out what you already hold, and how to ask a former supplier for the rest, calmly and in writing.

You paid for the system. Your staff use it every day, and your customers may log into it. So it is natural to assume your organisation owns it. Then the developer who built it moves on, someone asks for a copy of the code, and it turns out nobody inside the business has one, or the login to the hosting account, or any idea whose name the domain is registered in.
This is a common position, and in most cases it can be put right with a few weeks of patient, practical work. This article explains what "owning" a bespoke system really involves, how to find out what you already have, and how to ask for the rest. It is not legal advice, and the legal points below are a prompt to speak to your own adviser.
If your developer is still with you, our handover checklist is the better place to start. If they left recently, read our first-week guide alongside this one.
A working system is more than a program. To look after it, change it or move it to another supplier, your organisation needs control of several things:
You may have some of these and not others. That is normal. The aim is to know which, and to close the gaps in a sensible order.
Paying for software does not automatically mean you own the copyright in it. GOV.UK's guidance on ownership of copyright works explains the starting point: the first owner of copyright is usually whoever created the work. A freelancer or agency working under a contract for services will usually keep the copyright unless something else has been agreed in writing. Where the developer was your employee, your organisation as employer is normally the first owner.
In practice, many development contracts deal with this, either by assigning the copyright to the customer or by granting a licence to use and change the code. Some contracts say nothing at all. The system will also contain third-party and open-source components. Their authors or other rights holders keep the copyright, and your organisation uses them under each component's licence.
So the first job is to find the contract, the original quote or statement of work, and any terms and conditions you signed. Read what they say about intellectual property, source code and what happens at the end of the agreement. Then take your own legal advice on what they mean for you. Where the position is unclear, your adviser may suggest asking the developer for a short written assignment.
Before you ask anyone for anything, write down what you have. A simple table is enough:
| Item | Where it is | Whose name is it in | Who in your organisation has access |
|---|---|---|---|
| Source code | |||
| Hosting account | |||
| Domain name and DNS | |||
| Certificates | |||
| Third-party services | |||
| Database and backups | |||
| Passwords and keys | |||
| Documentation |
Some clues are easy to find. Your finance team's records will show which hosting, domain and software subscriptions you pay for, and to whom. Old emails often contain welcome messages from services set up for you.
Anything with a blank in the last column is a gap. Anything in the developer's own name, or paid on their card, is a gap even if it works today.
Most developers and agencies are happy to hand things over when asked clearly. A calm, specific request works far better than a general one.
Once credentials arrive, plan to change them. The developer may have done nothing wrong, but good practice is that nobody outside the organisation keeps access they no longer need.
Sometimes the email goes unanswered. Before assuming the worst, check Companies House to see whether the company is still active, and try any other contacts you have.
If the company has been dissolved, GOV.UK explains that its assets, including intellectual property, pass to the Crown as ownerless property, known as bona vacantia. In England and Wales, the Government Legal Department has a process to buy intellectual property that belonged to a dissolved company, and in some cases a company can be restored to the register. These are routes to discuss with your legal adviser rather than to attempt alone.
For accounts, work through each provider's own account recovery or ownership process, and be ready to show your invoices and company details. Where your organisation pays for a service, that is often a good starting point. Do not try to guess passwords or get into accounts you are not authorised to use.
Throughout all of this, the system usually carries on running. You have time to do it properly.
Getting a copy of the code is a big step, but it is not the end. You need to know that it is complete, and that it is the same version as the one your staff are using.
If any step fails, you have found a gap while things are calm, which is the best time to find one.
When Eastpoint looks after a system, the code and documentation stay in the customer's own repository, with a named engineer accountable for it and a named backup who also knows it. Our page on taking over from another supplier describes how we approach that first stage.
This week, you could:
If you would like an independent view of what you hold and what is missing, a software health audit is a good place to start, and our software care page explains how we look after systems once they are back in your hands.

A week-by-week plan for your first month with an inherited .NET application: access, a clean build, backups, tests, releases and monitoring.
· 8 min read
A fair tour of .NET 11 and C# 15 as released on 10 November 2026, the breaking changes to read first, and a decision guide for production teams on .NET 10.
· 7 min read
As of 10 November 2026, .NET 8 and .NET 9 no longer get security fixes. What has changed, what has not, and a calm 30-day plan for software on them.
· 4 min read