An unsupported database and the applications that depend on it
A SQL Server 2016 or Oracle database moved to a supported platform, with applications repointed, data reconciled and performance tested against today's workload.
Legacy system migration
Legacy systems, modernised in 30-day sprints.
Fixed-price 30-day sprints from A$50,000 for SAP, mainframe, IBM i, database and application estates, one defined scope at a time. A senior team, and you own everything we build.
30 daysper sprint, kick-off to cutover
- Fixed priceAgreed in writing before work starts
- 30 daysPer defined scope, from kick-off to live
- Parallel runOld and new side by side until the numbers match
- You own itCode, data, documentation and credentials
What is legacy system migration?
Legacy system migration is the move of business software, data and integrations from an ageing or unsupported platform, such as SAP ECC, a mainframe, IBM i (AS/400) or an old database, to a modern, supported one, without losing data or disrupting operations. A migration can rehost a system on new infrastructure, move it to a new database or runtime, rebuild its code, or wrap it in modern APIs so new channels can use it while the core is replaced in stages.
Sovereign Systems Labs delivers migrations as fixed-price 30-day sprints from A$50,000. Each sprint moves one defined scope, runs old and new in parallel until the data reconciles, and cuts over with a rehearsed rollback plan. Larger estates move in consecutive sprints.
It suits organisations with a system that is out of support, costly to run or blocking new work, and leaders who want a fixed cost and a signed-off result each month.
Waiting is the expensive option.
End-of-support dates rarely move in your favour. After them you pay more for less: premium support, paid security patches, or none at all.
31 Dec 2027
SAP ECC 6.0 on enhancement packages 6 to 8 leaves mainstream maintenance. Optional extended maintenance to the end of 2030 costs an extra two percentage points on your maintenance basis.
Source: SAP News, 4 February 2020
14 Jul 2026
SQL Server 2016 left extended support, so security updates now need paid Extended Security Updates. SharePoint Server 2016 and 2019 left support the same day.
Source: Microsoft Lifecycle
About 80%
of US federal IT spending goes on operating and maintaining existing IT, according to the US Government Accountability Office, including legacy systems, leaving little for anything new.
Source: US GAO, GAO-23-106821
Why legacy programmes stall
Most organisations know the old system has to go. The programme they are offered is usually the problem.
- Scoped in years, so the business case is stale before anything goes live
- Billed on time and materials, so every surprise becomes a change request
- One big-bang cutover at the end that nobody wants to sign off
- Knowledge of the old system held by a handful of people
We cut the work into 30-day sprints you can fund, test and sign off one at a time.
How a 30-day migration sprint works
One defined scope, five stages, and a decision point you control before anything is switched over.
- Before you sign
Migration Blueprint
Five business days to inventory the system, profile the data, map every integration and agree a fixed scope, price and cutover date.
- Week 1
Map and secure
Access, environments and security controls in place. Target design confirmed. Data mapping and acceptance tests agreed with your owners.
- Week 2
Build and wrap
The target platform is built. Code is moved or rebuilt, and APIs are wrapped around anything that stays, so other systems keep working.
- Week 3
Migrate and reconcile
Data moves in rehearsals. Record counts and totals are reconciled against the source and signed off by the people who own them.
- Week 4
Run in parallel, then cut over
Old and new run side by side. You make the go or no-go call, we cut over with a rehearsed rollback, then two weeks of hypercare.
A sprint, not a programme
Multi-year programmes made sense when every change was expensive. Most of the risk in them now comes from their size.
| Factor | Traditional multi-year programme | 30-day migration sprint |
|---|---|---|
| Pricing | Time and materials, plus change requests | Fixed price per sprint, from A$50,000 |
| First live result | Often a year or more | 30 days from kick-off |
| Commitment | A long contract before value is proven | One sprint at a time. Stop between sprints whenever you choose |
| Cutover | One big bang at the end | Parallel run, reconciliation sign-off and a rehearsed rollback |
| Team | Large teams and many hand-offs | Senior specialists assembled around your system |
| What you keep | Proprietary accelerators you keep paying for | All code written for you, data, documentation and runbooks |
General characteristics of large multi-year programmes, shown for comparison. Not a statement about any particular firm.
What we migrate
From almost anything, to something supported.
SAP ECC to S/4HANA
Custom code, data and interfaces moved in fixed-price waves before mainstream maintenance ends on 31 December 2027.
SAP HANA
Databases moved to HANA, upgraded or rehosted, with downtime measured in rehearsals.
Mainframe and COBOL
Workloads moved off, or opened up with secure APIs while the core is retired in stages.
IBM i (AS/400)
Green-screen applications rebuilt for the web, or upgraded off IBM i 7.4.
Databases and warehouses
Moved to PostgreSQL, Azure SQL, Aurora, Snowflake or Databricks and reconciled table by table.
Legacy applications
Rebuilt as secure web applications with single sign-on and audit trails.
API wrappers and integration
Modern, secured APIs around the systems that stay, so new channels and AI can use them now.
Cloud and infrastructure
Unsupported servers and on-premise platforms moved to supported, Australian-hosted cloud.
Common migration paths
The target is chosen for your licensing, skills and risk, not ours. We do not resell software.
SAP ECC 6.0 to SAP S/4HANA, on-premise or RISE
SAP on Oracle, DB2, SQL Server or MaxDB to SAP HANA 2.0
SAP BW 7.x to BW/4HANA, Datasphere or a lakehouse
SAP PI/PO 7.5 to SAP Integration Suite
COBOL, CICS, JCL and VSAM to Java, .NET or cloud services, or wrapped APIs
IBM i RPG and DB2 for i to Web applications on a modern database
Oracle Database to PostgreSQL or Amazon Aurora
SQL Server 2014 or 2016 to A current SQL Server, Azure SQL or PostgreSQL
Teradata or Netezza to Snowflake, Databricks, BigQuery or Fabric
VB6, Delphi, PowerBuilder or Access to Secure web applications on .NET 10 or TypeScript
Lotus Notes and Domino to Microsoft 365 or a purpose-built web app
Windows Server 2012 or 2016, RHEL 7 to Supported platforms in Australian cloud regions
Engagements
Three ways to start
Migration Blueprint
from A$9,500
System inventory, data profile, integration map, risk register and a fixed-price sprint plan with a cutover date. Fully credited against your first sprint if you go ahead within 60 days.
Book a Blueprint30-Day Migration Sprint
from A$50,000
- One defined scope, live in 30 days
- Security controls from day one
- Parallel run and reconciliation sign-off
- Rehearsed rollback and cutover
- Two weeks of hypercare after go-live
- All code, data and documentation handed over
Migration Waves
from A$50,000 per sprint
Large estates, such as a full S/4HANA conversion or a mainframe exit, moved in a planned sequence of fixed-price sprints. Each one is signed off before the next begins, and you can pause between them.
Plan your migration wavesPrices in Australian dollars, excluding GST. Scope and fee are confirmed in writing after the Blueprint.
What fits in 30 days
Illustrative examples. Your scope is confirmed in the Blueprint, and if it does not fit in 30 days, we tell you before you sign.
An Access, VB6 or Lotus Notes application, rebuilt
Rebuilt as a secure web application with single sign-on, role-based access and audit logging, and the data migrated across.
A mainframe or IBM i function, opened up
Documented, secured APIs around a core transaction, so new channels and partners stop waiting on green screens.
One SAP migration workstream
A custom code remediation wave, a data cleansing and load cycle, or a set of PI/PO interfaces moved to SAP Integration Suite.
A Windows Server 2012 or 2016 workload
Moved to a supported operating system or cloud platform, with backups, patching and monitoring in place.
Safeguards in every sprint
Security from day one
Least-privilege access for the sprint only, encrypted transfers, and every credential removed when we finish.
Nothing switched off early
Your old system stays available until the new one is reconciled and signed off.
Reconciled, then signed
Record counts, totals and sample checks signed off by your data owners before cutover.
A rehearsed way back
Every cutover has a tested rollback plan, and the go or no-go decision is yours.
No lock-in
Open, documented platforms. Code, data, runbooks and credentials are all handed over.
Your data stays onshore
Australian data residency by default, and a mutual NDA before discovery.
449days left
SAP ECC leaves mainstream maintenance on 31 December 2027.
Most SAP landscapes need several workstreams, such as custom code, data, interfaces and BW, each taking one or more 30-day sprints. Starting now leaves room to do each one properly.
Further reading
Can a real migration happen in 30 days?
Yes, when the scope is right. Each sprint moves one defined system, database, application or workstream. The Migration Blueprint confirms what fits before you sign. Larger estates, such as a full SAP S/4HANA conversion, move in consecutive sprints, each live and signed off before the next begins.
What does a sprint from A$50,000 cover?
One fixed-price sprint: confirmation of the scope, the target build, data migration with reconciliation, APIs for anything that stays, security controls, a parallel run, cutover with a rehearsed rollback, two weeks of hypercare and full documentation. The fee for your scope is confirmed in writing after the Blueprint. Prices are in Australian dollars and exclude GST.
What happens if the work takes longer than planned?
The price is fixed for the agreed scope, so overruns within that scope are our cost, not yours. New work you ask for is quoted before it starts, or moved into the next sprint.
Will our operations be disrupted?
Old and new systems run in parallel, cutover happens at a time you choose, and a rehearsed rollback is ready. You make the final go or no-go decision.
Who does the work?
A team of relevant professionals assembled around your system and led by our principal: SAP, mainframe, database, cloud and security specialists, as your scope requires.
How do you keep our data secure during a migration?
Least-privilege access granted for the sprint only, encrypted transfers, Australian data residency by default, a mutual NDA before discovery, and all access removed and confirmed in writing when we finish.
Are you an SAP, IBM or Microsoft reseller?
No. We are independent and do not resell licences, so our advice is not tied to a vendor's sales targets. Where a licence or subscription is needed, you buy it directly from the vendor or your existing reseller.
Do you work with our IT team and existing suppliers?
Yes. We work alongside your internal team, managed service provider and software vendors, and hand everything over so your people can run the new platform with confidence.
Find out if your system fits a 30-day sprint.
Tell us what you run and when it needs to move. We reply within one business day with initial thoughts and times to talk, and we are happy to sign an NDA first.
We take on a limited number of engagements each quarter so every sprint has a senior team.
Prefer email?
contact@sovereignsystemslabs.com