There are several good reasons for wanting to migrate your legacy web system – for example to:
Recent advancements have made migration relatively straightforward for most systems developed today. In contrast legacy systems may not have been written with portability and platform-independence in mind – which means getting them to play ball on new hardware can be much more of a challenge. That’s where our solid experience in migrating legacy systems can come to the rescue. We can take away the headache and get your new deployment up and running quicky, leaving you free to focus on moving your business forward.
You may want to undertake this kind of migration if your current system is suffering from low remaining disk space, insufficient bandwidth or poor connectivity, or you want to benefit from more modern hardware (e.g. SSD). Migration to a standalone target is usually the simplest because the new deployment is unlikely to clash with existing processes. However some common challenges that may still need addressing are:
Migration to a standalone target machine can often be done quickly and painlessly, and is usually inexpensive. Get in touch with us via email at
Substantial code-base incorporates some complexity and a variety of coding styles – mainly due to the number of years of operation… Hardcoding appears minimal in packages, which generally refer to config files. However hard-coding is widely prevalent in the older scripts, and this is likely to be the main issue which needs addressing, particularly as the new setup will be accessed directly rather than via a network… [Migration] should be straightforward as the client does not require the OS or other components to be upgraded…
You may wish to do this to improve efficiency, if systems interact frequently – alternatively you may be conscious of unused disk space or bandwidth, and be aiming to reduce cost. Putting systems on the same server allows rapid, timeout-free interaction and can reduce overall disk usage through shared resources. However the more resources are shared, the more care needs to go into ensuring components cooperate smoothly. Typically uniting separate systems on the same server involves facing the same hurdles as migrating to a standalone machine, but with some additional challenges. Some examples are ensuring
Depending on your platform loads, uniting systems on the same server may be more complex to implement than deployment on fresh server space – however we have the expertise to deliver a solution safely, quickly and at minimum cost. To find out more about your own situation, email us at
This is often more involved than a simple hardware migration, but there may be several legitimate reasons for implementing it. Some examples are:
Many real cases of hardware migration also involve some elements of software migration, as it is not always possible or desirable to keep source and target software identical. The greater the change in underlying software, the more complex the migration may be. It is worth pointing out that this can still apply with systems that have been built with tools that are theoretically platform independent (e.g. Java). If you are considering a migration involving a significant software change, then we can help. Send us an email at
[This is a] concise REST based payment service interface for a larger e-commerce site, operating as a pair of Perl-Catalyst applications… The service routes payment requests to various payment gateways based on settings controlled via a basic web GUI. The REST payment application is more extensive but is written in a single language and is reasonably consistent… It’s unlikely there will be an issue moving from Perl 5.10 to 5.18. The client has expressed a desire to integrate the few remaining CGI scripts into the main Catalyst application as part of the migration process. This looks to be mostly a matter of moving script subs into modules, but it is advised that the existing test framework be extended to cover the new code. Ubuntu server 14.04 ships with Apache 2.4 as standard, so Apache config files will also need manually going through and updating as 2.4 is not completely compatible with 2.2.