Service · Custom software

System and database migration

Suppose a haulage firm in Wels runs its transport management on Oracle 11g, installed on Windows Server 2012 R2. Neither receives security patches any more, the Oracle licence is expensive, and every year the insurer asks when it will finally be replaced. The application itself is stable. The real risk lies in everything bolted on over the years: dispatch spreadsheets querying the database directly, a telematics interface, nightly exports for accounts and stored procedures nobody fully understands any more. Moving to PostgreSQL in an EU data centre saves licence fees and closes security gaps, but only succeeds if those dependencies are known beforehand. We carry out the work over remote access and plan the switch so that operations ideally pause for no longer than a weekend.

Oracle, SQL Server
to PostgreSQL or a current release
Delta sync
for short cut-over windows
2 rehearsals
at full data volume
7 years
archive planned for the BAO

Everything this covers

Moving the data itself is often the smallest part. The effort lies in dependencies, converting code and proving that everything arrived intact.

Settle the details with an engineer

Uncovering dependencies

We analyse database logs to see which programs, macros and users actually connect, including the ones IT never knew about.

Modernise or relocate

A straight move to a current version, a switch of database engine or replacing the application at the same time. We set out the effort and risk of each.

Converting schema and code

Data types, sequences, stored procedures and triggers are translated, for example from PL/SQL to PL/pgSQL, and protected by tests.

Cleaning data

Duplicates, orphaned records and broken character encodings are dealt with before the move, so the new system does not inherit old problems.

Short downtime

The bulk of the data is copied in advance, and on switch day only the changes since the last sync are transferred. Days often shrink to a single night.

Performance comparison

Key queries and reports are timed before and after. If anything slows down, we tune indexes or queries before users notice.

Archiving the old system

To satisfy statutory retention, a readable copy is kept, either as a read-only database or exported to open formats.

Our working method

No rehearsal, no switch. Only measurements against your real data volume reveal how long the outage will be.

01

Analysis

Inventory of database, code and access, choice of target platform and a plan covering risks and costs.

02

Conversion and testing

Schema and code conversion, automated comparison of data sets and checks of key processes by your users.

03

Rehearsals

At least two full runs with timings, followed by a fixed runbook for switch day.

04

Cut-over and aftercare

The switch in the agreed window, a fallback on standby and a few weeks of closer support.

Let your business departments test, not just IT. Technical comparisons prove every record has arrived. Whether dispatch's monthly report still shows the same figures is something only dispatch will notice. Give each department a short checklist and a few hours of testing time before the switch date.

Frequently asked questions

Frequently, since licence costs disappear and PostgreSQL holds its own for most business applications. It is not worthwhile if a packaged product supports only one specific database. We check that first.

With delta sync, one night or a weekend is enough for many systems. We know the exact duration after the second rehearsal, and you receive a timed plan with decision points beforehand.

The old system remains reachable in read-only mode, and a fallback is ready for as long as it makes sense. Individual missing records can be pulled across from the legacy data.

Not necessarily. It often makes sense to migrate only the active years and leave the rest in an archive that satisfies retention rules. That keeps the new system lean.

Wherever you choose: data centres in Austria or the EU, such as Exoscale, Anexia or Hetzner, or your own infrastructure. You sign a data processing agreement with the provider.

Let us plan your move

Which system or database is being replaced, and how long can the business stand still? We begin with an analysis.

Availability
Monday to Friday, 8:00-17:00 Austrian time (CET/CEST), reply within one working day
Meetings
By video on Microsoft Teams or Google Meet

We only use cookies that are technically required: to run the website and to remember the location you picked. There are no advertising or tracking cookies. Details are in the privacy notice.