Get rid of that old junk: modernize your legacy software in 5 steps

Let’s be honest: most IT projects don’t fail because of the technology, but because of people. That’s why from day one we focus on knowledge transfer. We don’t just build your new software; we make sure you can continue on your own afterwards. Here's how.

Step 1: mapping out the current situation

We always start by mapping out your current processes and IT landscape. What still works? Where do things get stuck? I often see family businesses wanting to completely get rid of their legacy application. “Get rid of that old junk!” A logical thought, but that old junk contains a lot of business knowledge. You don’t just throw that away.

That’s why we first map your entire IT landscape. Which systems talk to each other? Which processes are truly unique to your company? We literally walk the floor, from the warehouse to the boardroom. Only then do we really understand what needs to happen and which processes or tasks must be preserved.

Step 2: upcycling your old software

Here’s the magic: we usually don’t have to reinvent the wheel. With Thinkwise upcycle technology, we convert your existing application into a modern version quickly. It may sound like science fiction, but it really works. Your old business logic is translated into new technology. Within a week we have a proof of concept, so you can immediately see what we can build. No vague PowerPoint slides, but tangible, working software.

Step 3: your developer becomes our colleague

This is crucial: we require you to hire a developer of your own. “But we don’t have anyone with Thinkwise experience,” I often hear. That’s not a problem. We train them, and from day one they work with our team. We don’t start without your own developer. Why? If we go live successfully after a year, we want you as an organization to continue developing the application yourself. And if your developer has been involved from the start, they can later handle updates and extensions with ease.

Step 4: go live in phases

Forget the big bang go live where your entire company has to switch to completely new software in one weekend. We work step by step. First we migrate your current processes one to one. Yes, including that 1995 workflow no one dares to change.

Why? Because your people need to get used to the new system first. If everything looks the same but works ten times faster, you have an immediate success moment. After that, we improve process by process. We deliver a new release every month, with improvements your people actually want and look forward to.

Step 5: from building to independence

After a few months, something great happens at most companies. Your developer starts coming up with their own ideas. “Couldn’t we just…” they begin. Yes. That’s the moment I know it will work out just fine.

Because you didn’t just buy new software; you now have an in-house software factory. A recent example? One client realized they could save €30,000 a year in licenses by building three small tools themselves. Their developer had it running within a month.

The red flags we watch out for

But it’s not all sunshine and roses. I often see companies wanting too much in too little time during projects like this. “Since we’re at it, can’t we also…” Stop. That tempting thought has been the root of all evil in more projects than any technical challenge. At the start we set priorities and we don’t deviate from them lightly.

Another killer is the mentality of “we’ll just do it on the side.” A product owner is not a side task for the subject-matter expert who also has their day job. Training a developer doesn’t work if they are available only one day a week. Halfhearted effort leads to halfhearted results.

What do you get out of it?

After a year I always check in with these clients. What I see are companies that build, improve, and innovate on their own. That dependence on external consultants? A thing of the past. One client told me recently: “In the past we didn’t dare dream of new functionality. Now we come up with it on Monday and by Friday it’s there.”