Legacy Update

It's not about tinkering with your strategic systems; it's about bringing bespoke enhancements up to date so you can move on .

We are talking about bespoke software here, not wholesale replacement of a Practice Management System or major data conversions. The consultancy, development, customisation and implementation tasks associated with upgrades or your strategic platforms are almost always best left with the suppliers of those platforms themselves.

So what is "Legacy Update"

It's a review of legacy software and how the solution it provides might best be brought up to date. Kutana are past masters at reading other people's undocumented code, working out how best to effect required changes and proposing or implementing solutions to suit the need.

Even if the source code is not available, don't think you are stuck with ageing software. There is always a way of achieving what you require.

We are equally comfortable working directly with end users, IT solution providers, in-house or externally-written code.

How about some examples?

• You have a bespoke reporting system that uses Exchange Server 5.1 to send reports out to support staff in international offices. The upgrade to Exchange Server 2003 has broken the software and the developers are no longer available.
• You have sophisticated suite of templates with macros in WordBasic which integrate with your DMS. You are upgrading the DMS but don't want to lose any of the current functionality you have in the templates.
• You have a suite of complex queries written for SQL Server. You need some enhancements to them but have no idea how they work or who could make the changes for you.
• You have a nice piece of fee earner software for conflict searching. It was written for 16-bit Windows and it still works but it needs some enhancement. The developer disappeared years ago and you have the source code but no-one to make the changes you require.
• You have a system of synchronisation routines that keep your PMS in step with your extranet. Your PMS is being replaced and, although the PMS supplier has offered to rewrite the synchronisation, you wonder if there might be a less dramatic, cost-effective solution.
• You have a shared database to manage and report upon CPD records. It needs a few changes. It could be replaced but that would mean a whole new implementation. You would like to find out if you can keep it simple by making the alterations to the current system.
• You have a sophisticated Excel model for draft billing but no-one knows how it works. You would like it to be changed or replaced and need help in determining the options. If it ends up being changed you would certainly like some documentation for it.
• You are happy with your PMS but you want to provide regular data extracts for online reports. For some reason you are no longer happy to work with your PMS supplier to achieve this.

Supported Platforms

Microsoft Windows, Delphi (1 upwards), VB, VBA, ASP, WordBasic, Microsoft Office (4.3 upwards), SQL Server, Exchange Server, WordPerfect (5 upwards) and many others...