Replacing Existing Systems and Spreadsheets

Yes. Access is one of the most common systems we replace. We treat your current database as the prototype, keep the workflow your team knows, and move the data onto a modern database server without Access’s size limits or corruption risk.

Yes. We study what your current system does and carry its business rules and data across, rather than rediscovering everything. Where it makes sense, we replace the system in stages instead of all at once.

Yes. We migrate applications built in Access, Visual Basic 6, Delphi, FoxPro and Classic ASP onto supported, modern platforms. Sometimes a short-term fix such as a virtual machine buys time, and we will tell you if that is the sensible first step.

Yes. Our systems are designed for many users working at once, from the office, from home or on site, with access matched to each person’s role.

Yes. Data migration is part of the project, not an optional extra. We move your records, history and reference data across and check them against the old system before you switch. We can only do this if we can get access to the old system’s data, and we will tell you before you sign up for the project if we can’t.

No, as long as we can migrate the data. Your history comes with you. We validate the migrated data, and during parallel running you can compare the new system against the old on real work.

Usually, yes. We have integrated with accounting systems including Xero, MYOB, QuickBooks and Saasu, and can connect to other systems that offer an API or a data export. We confirm what is possible during scoping.

Yes. Your existing system stays live and remains the system of record until you decide to switch. In staged replacements, parts of the old system keep running until their replacement is ready.

We keep it to a minimum. Near the end, both systems run side by side for a short period, which means some duplicate entry, then we switch when you are satisfied.