Across Sweden, Denmark, Finland, and the broader Nordic region, enterprise IT leaders are navigating one of the most significant technology decisions of the decade. With the SAP ECC mainstream support deadline of December 2027 fast approaching, and optional extended maintenance available until 2030 only at an additional premium and with a significantly reduced scope, the question of how to migrate, not just when, has never mattered more. While the extended support bridge exists, it offers no new features and limited legal updates, making it a temporary holdover rather than a strategic destination.

For many complex, data-heavy environments across the Nordics, the planning phase is hitting a critical crunch point. Market data shows that roughly 35% of larger enterprises remain in the exploration or planning stage. Given that a typical enterprise migration timeline spans 18 to 36 months, 2026 has officially become the decision year that dictates how 2027 unfolds. 

Most organisations find themselves weighing two familiar, traditional approaches. Yet, there is a third path beginning to attract attention among forward-thinking organisations that want a cleaner, more deliberate view of their future system landscape.

The Limits of the Traditional Approach

For years, the S/4HANA roadmap has been presented as a binary choice: System Conversion (Brownfield migration) or New Implementation (Greenfield migration).

A System conversion (Brownfield) is often perceived as the lower-risk, more comfortable route. It leaves your existing configuration, custom code, and historical data structures largely intact. However, for Nordic firms with decades of accumulated SAP history, a pure lift-and-shift conversion comes with a hidden cost.

Legacy SAP environments are frequently a complex compilation of small operational decisions made over generations, resulting in overlapping logic, orphaned custom code, and unoptimised data ownership. Choosing Brownfield means carrying that entire historical pile of technical debt and process inefficiency directly into your expensive new S/4HANA environment.

Conversely, a New Implementation (Greenfield) offers a completely fresh start. You build a brand-new system from scratch, redesigning business processes to fit modern best practices. The catch, of course, is the sheer scale of the investment. Rebuilding configurations, mapping entirely new processes, and abandoning historical data altogether requires immense organisational disruption and capital expenditure – an investment that isn’t always justified for stable businesses.

For some organisations, one of these approaches will be the clear answer. But for many complex, data-heavy landscapes, neither extreme fits comfortably: a system conversion (Brownfield) means carrying forward decades of accumulated clutter, while new implementation (Greenfield) means walking away from configurations and processes that still work perfectly well. If that trade-off feels familiar, it’s worth knowing there’s a middle path.

Introducing the Hybrid SDT Approach

This brings us to the Selective Data Transition (SDT) approach, often referred to as the Hybrid Approach. Rather than treating migration as an all-or-nothing choice, SDT combines the structural benefits of a system conversion with the clean-data advantages of a new implementation.

To look at it through a simple house remodeling analogy: if your corporate system is a decades-old family home, a system conversion (Brownfield) approach means moving into a new house but packing up every single piece of old furniture, broken appliances, and basement clutter to bring with you. A new implementation (Greenfield) means demolishing the entire house, throwing away all your belongings, and building a completely new structure from scratch.

The Hybrid SDT approach offers a third way. It allows you to keep the strong architectural foundations of your home, modernise the specific rooms that need a redesign, and selectively pack only the valuable, clean belongings you actually need for the future.

Unsure whether to lift-and-shift decades of accumulated SAP history? Let’s assess your data landscape together and identify what to carry forward and what to leave behind.

In practice, the SDT framework unfolds across a controlled, four-step methodology:

  1. Shell Creation: We take a copy of your existing production system configuration and repository without any of the underlying transactional data.
  2. Harmonisation & Adaptation: This empty shell is upgraded to S/4HANA, giving us a sandbox to optimise data structures, strip out redundant custom code, and consolidate multiple legacy systems into a singular client.
  3. Selective Migration: Instead of migrating your entire database, we strategically extract and load only the data that serves your current business strategy. For example, you might choose to migrate active master data and only the last three years of transactional history.
  4. Cutover & Go-Live: The optimised data and consolidated systems are brought live on the new platform.

For Nordic enterprises prioritising data sovereignty and system consolidation, this methodology offers clear financial and operational advantages. By moving only what matters, you dramatically minimise your active in-memory HANA storage costs, reduce project timelines, and establish a highly accurate, clutter-free data foundation that is perfectly primed for advanced AI and analytics.

Explore how a unified Hybrid migration cutover can streamline your consolidation strategy in a single step.

Is it Right for Your Organisation?

The Selective Data Transition approach is an emerging methodology that is not a universal option for every business. At GlueData, we are currently actively building our core competency in SDT migrations, and we evaluate its application with strict realism. It is not inherently superior to a system conversion (Brownfield) or new implementation (Greenfield) approach; it is a highly specialised alternative designed for specific enterprise circumstances.

SDT is worth exploring if your organisation fits the following profiles:

  • Data-Heavy Complexity: You have massive volumes of historical or obsolete data that would needlessly bloat your S/4HANA infrastructure costs.
  • System Consolidation Goals: You are running multiple SAP instances across different countries and want to merge them into a unified cloud landscape in a single, streamlined step.
  • Corporate Restructuring: Your business is planning or undergoing active corporate carve-outs, divestitures, or structural mergers.

Ultimately, the right path depends entirely on your specific landscape, data quality, timeline, and long-term commercial goals. Finland leads the region with nearly 80% cloud adoption, while Sweden and Denmark consistently rank in the top five globally for digital innovation. In markets that evaluate technology strategies strictly on merit and long-term ROI, the Hybrid path stands out as a choice to explore.

If you’d like to explore whether a hybrid Selective Data Transition approach fits your data landscape, let’s talk.