Service · Custom software development

Application and database migration

With a live system you get exactly one attempt. That is why most of the effort goes into preparation: full rehearsals, timing of every step and a finished plan for going back. The move itself is carried out remotely, and we stay online from start to finish.

Send an enquiry See the scope

Dress rehearsal

before the real move

Window

based on measurements

Rollback

prepared in advance

Reconciliation

straight after cutover

What the service covers

Preparation decides the outcome. The move itself takes a few hours, but getting ready for it takes weeks.

Talk it through with us

Inventory

What is moving, what it depends on, where data lives and which integrations will be affected.

Plan

Steps in sequence with time estimates and checkpoints where the go or no-go decision is made.

Rehearsals

A full migration to a test environment, timed, with a hunt for bottlenecks.

Conversion

Integrity checks and data transformation wherever the new system is structured differently.

Rollback

Documented actions for the case where a serious problem appears after cutover.

Reconciliation

Totals, row counts and spot checks on what matters most, such as open items and customer balances.

How we deliver it

Preparation takes two weeks or more. The move itself can usually be completed over a weekend.

Assessment

Data volume, dependencies, integrations and how much downtime the business can tolerate.

Dress rehearsal

A full run on a copy with a stopwatch. The first rehearsal almost always uncovers surprises.

Migration

Carried out in the agreed window following the rehearsed script, with a named contact online throughout.

Aftercare

We watch the system closely for a week, and the old one remains available for comparison.

Do not switch off the old system the day after migration. Keep it running, or at least accessible, for a minimum of 30 days. Something that did not come across, or came across wrongly, nearly always turns up, and you need somewhere to retrieve it from. Remember to update your record of processing activities if personal data has changed location.

Common questions

The rehearsal gives the exact figure, because it measures your real data volume. In our experience, databases of up to a few hundred gigabytes move in a matter of hours, ideally over a weekend.

For some systems, yes, using continuous synchronisation and a quick final switch. It is more expensive and complex and is justified where downtime is genuinely unacceptable. Most businesses are fine with a weekend window.

That is why a full backup is taken before we begin and a reconciliation is done afterwards. The backup stays untouched until you confirm everything works as it should. There is a point to return to at every stage.

Yes. Many clients use a migration to consolidate data in EU data centres. We plan the location with you so it matches your GDPR documentation.

Related services

View the whole area

Service End-to-end development Discovery, design, code, testing and ongoing care from one team Service Mobile app development iOS and Android apps published under your own accounts Service Open source development No per-user licence fees and no single-vendor lock-in Service Dedicated development teams Developers and testers in your team without hiring

Let us plan your migration

Tell us what is moving where and how much downtime you can accept. We start with a rehearsal on a copy.

Email
office@apply.dk

Coverage
All of Denmark, delivered remotely

I agree that Apply may handle my details as set out in the privacy policy