We take over old custom software when the developer is gone.

Someone built a program for your business years ago. It still runs the shop, the billing, or the scheduling, and now that person has retired, moved on, or stopped answering the phone. Nobody left at your company knows how it works. Norsoft is a custom software firm in Mankato, Minnesota, and taking over software in exactly that condition is work we have done since 1987.

You are not starting over. You are getting the keys back.

Most owners in this spot assume the only options are to keep limping along or to throw the whole thing out and spend a year replacing it. There is usually a third option, which is to understand what you already have well enough to make a real decision about it. The system is running your business today, which means it works, even if nobody can explain why.

The risk is not that the software is old. The risk is that one person understood it and that person is gone, so the next time it breaks there is nobody to call, and the business stops while you look for someone willing to open a codebase they have never seen.

What we do first

We start by taking control of the system so it cannot get worse. That means getting a backup of the source code and the database, identifying what language and database it was built on, and getting a copy running somewhere safe where we can test without touching your live operation.

Then we document it. What it does, what talks to it, where the data lives, which scheduled jobs run overnight, and which licenses, domains, and passwords the business needs to actually own. A lot of takeovers turn up an expired license or an account still in a former employee's name, and it is better to find that now than during an outage.

When that is done, you get a straight recommendation: maintain it as is, repair the parts that are failing, modernize it piece by piece, or replace it. We will tell you which one we think is right and what each would cost you, including when the honest answer is that it is fine and you should leave it alone. We wrote about how to make that call in software project rescue versus starting over, and about the first steps to take in the first 48 hours after your developer disappears.

Then we keep it running

Once we know the system, we fix the urgent problems before anything else, and after it is stable we improve it on your schedule rather than ours. If you want us to hold it long-term, the same people who documented it stay on it. If you ever want to hand it to an internal team or another vendor, you get the documentation and the accounts, and the handoff is clean. You own the code either way.

Two real takeovers

A veterinary supply distributor facing a federal deadline. Hazardous materials shipping rules were about to put them out of compliance. Because we already knew their system, we deployed real-time compliance validation in 24 hours. The full story is here.

A pricing engine nobody else could untangle. We took over a broken five-tier pricing system, rebuilt it, and it has run clean since. Read what that involved.

This is probably you if

• The developer who wrote your software retired, left the company, or stopped returning calls
• Nobody at your company can explain how the system works, and the documentation is a folder nobody has opened
• You are afraid to change anything because you do not know what it will break
• A vendor delivered something that looked right in the demo and falls apart in real use
• You want an honest answer about whether to keep it, fix it, or replace it