In brief

An older FileMaker system does not necessarily need replacing simply because of its age. The better question is whether it still fits the business, the people who rely on it and the technology around it — and whether improving, integrating, restructuring or replacing parts of it could solve existing problems while keeping the door open to future opportunities.

An old system is not necessarily a bad system.

If your FileMaker system has been supporting the business for years, the question is not simply whether it is old. The more useful question is whether it still supports the way the business needs to work today.

Sometimes the right answer is replacement. Sometimes it is a few carefully chosen improvements. That might include changing how part of the system works, improving reporting, or expanding the way it connects with other applications.

And sometimes most of the existing system is still doing its job perfectly well.

Before deciding what to change, it helps to understand what has changed, what is getting in the way, and what opportunities the business may now want to pursue.

Start with what has changed

The decision should not begin with “old or new”.

It should begin with what has changed in the business, what is getting in the way, and what the business now needs from the system.

Perhaps reporting is slow. Information is being entered more than once. A process has become awkward. One person knows too much about how the system works. An integration is unreliable. Or changes that once seemed simple have become difficult and risky.

But the issue may not be that the system has deteriorated. The business itself may have changed. There may be more staff, new services, different customers, new reporting requirements, or other applications that now need to share information with FileMaker.

There may also be new opportunities that the existing system was never expected to support.

Once those changes are understood, it becomes easier to decide what actually needs attention.

That might mean maintaining the existing system, improving part of it, expanding its integration with other applications, rebuilding something in stages, or replacing it altogether.

Understand what you already have

Older systems often contain years of practical knowledge about how a business works.

If the system is stable, understood by the people who use it, and still reflects the way the business operates today, targeted improvements may deliver far more value than a full replacement.

Over time, a system can also accumulate a great deal of business knowledge — how unusual situations are handled, why particular processes exist, what different people need from it, and how different parts of the business fit together.

That knowledge has value and should be understood before deciding what to change.

A small change can sometimes remove a large frustration.

That might involve automating a manual step, improving reporting, adjusting a workflow, expanding an integration, replacing an ageing component, or making the system easier to monitor and support.

The important point is that age alone does not determine value.

Look at the work around the system

Before changing the software, it is worth looking at the work and the wider environment around it.

Colleagues reviewing a document together

Sometimes the system itself is creating the problem. Sometimes it is simply exposing a process that has become more complicated over time. And sometimes the business has changed in ways the original system was never designed to support.

People may be copying information between places, maintaining additional spreadsheets, working around bottlenecks, or relying on memory because the original process no longer fits the business.

It is also worth looking at what has changed outside the system. The business may now use other applications, online services, customer portals, accounting tools, or cloud platforms that did not exist, or were not practical to connect with, when the FileMaker system was first built.

FileMaker itself may also be able to connect with more of those tools than was possible in the past. That can create opportunities to reduce double handling, improve visibility, extend what the existing system can do, or make new ways of working possible without replacing it.

Replacing the software without understanding the process, the business changes, and the technology around it can simply move the same problem somewhere else.

Know when to consider a different approach

There is also a point where continuing to patch and improve an existing system stops making sense.

Small changes may begin to carry too much risk. Workarounds may multiply. Important parts of the system may depend on ageing technology or knowledge held by only one person. People may become reluctant to make changes because they are unsure what else might be affected.

The wider environment also needs attention. A FileMaker solution may continue to work well while its hosting, access controls, backups, integrations, devices or other supporting layers need to change as security risks and expectations evolve.

At that point, the question needs to become broader than “How can we improve the FileMaker system?”

It is worth asking, “Is there a better way?”

A team discussing ideas at a whiteboard

That means looking at what the business is trying to achieve, how well the current process supports it, what the ongoing costs and risks are, what other technologies or approaches may now be available, and how well the chosen approach can adapt as the business changes again.

It also means considering opportunity. A good system should not only deal with today's requirements. Where practical, it should give the business room to respond when a new customer, service, market, process or idea creates an opportunity to do something differently.

A different application may suit part of the work better. A cloud service may remove the need to build something that can already be provided elsewhere. Better integration between systems may reduce duplication or make something possible that previously was not. Or the most sensible option may still be to keep FileMaker at the centre and improve the way it connects with the rest of the business.

The important question is not simply how old the system is, or whether it can still be made to work. It is whether the current approach remains the best fit for the business — functionally, financially and technologically, both now and into the future.

Change only what needs changing

Once the problem and opportunity are understood, it may become clear that the whole system does not need replacing.

Some parts may still work well and simply need to be adjusted to better fit the way the business now operates. A workflow might be simplified, a process reworked, or a function retuned to remove unnecessary steps.

Other areas may benefit more from better integration. Information that is currently copied between FileMaker and another application might instead be shared automatically. A new service or external application may be able to take over a particular function while FileMaker continues to handle the parts it already does well.

In some cases, part of the existing system may still need rebuilding or replacing. A reporting function might move elsewhere, an integration might be redesigned, or a customer-facing process might be separated from the rest of the system.

The aim is not to change everything simply because change is needed somewhere. It is to understand which parts still serve the business well, which parts could work better, and where a different approach would provide more value or create new possibilities.

Making changes in this way can reduce disruption, spread cost and risk, and allow the business to gain useful improvements without committing to one large replacement project.

Include the people who use and support it

Technical assessments only tell part of the story.

The people who work with a system every day often know where its real strengths and weaknesses are. So do those who depend on the information it produces, the processes it supports, or who are responsible for maintaining and supporting it.

A workflow that looks strange from the outside may exist for a very good reason. Equally, something that appears to be a small inconvenience may be costing hours of work every week or creating problems further along the process.

It is also important to understand the support side of the system. Is knowledge concentrated in one person? Are changes becoming harder to test or explain? Are there parts of the system that people are reluctant to touch because they are unsure what else may be affected?

Looking at the system from the perspective of users, managers, customers, suppliers, support people and others who depend on it can reveal issues and opportunities that are easy to miss from a purely technical review.

Understanding how people use, rely on and support the system helps avoid removing something useful while trying to fix something outdated.

It can also help reveal whether the real problem sits in the software, the process around it, the way people work with it, or somewhere in between.

Make the decision based on value

Modern technology can make a system easier to maintain, integrate and extend.

But being modern is not a business outcome by itself.

The aim is to understand what the business needs, what has changed, what opportunities may be available, and what will provide the most value now and into the future.

That may mean improving the existing system, changing the way parts of it work, expanding its integration with other applications, replacing selected functions, or moving to something different altogether.

Whatever approach is chosen, it should continue to support the way the business operates, remain secure and supportable within the wider environment around it, and give the business reasonable room to change.

A good system should not only help the business deal with today's work. It should also avoid unnecessarily closing the door on what the business may want or need to do next.

And because businesses, technology, risks and opportunities do not stand still, that fit should be revisited from time to time.

The most important question is not whether the system is old or new.

It is whether it remains relevant to the business, its people, the way they need to work — and where the business may want to go next.