Planning a SAP S/4HANA Implementation starts with one early, costly choice: the migration path. Once a team commits to a conversion, a rebuild or a phased approach, the budget, the partner contract and the project calendar all lock around that choice. Many organizations make it in a workshop, armed with opinions and a few strong personalities. However, a better method starts with evidence. For any SAP ECC to S4HANA Migration, the data in your own system should pick the path, not the loudest voice in the room.
What Does It Mean to Pick an S/4HANA Path With Data?
Choosing a path with data means scoring what your ECC system actually contains, mapping how those pieces depend on each other, and estimating effort for each object before anyone commits to a strategy. The result is a recommendation you can defend to a CFO and audit later.
Opinion-led decisions fail in predictable ways. A CIO who wants a clean slate pushes for greenfield. A finance director who fears disruption pushes for brownfield. Both may be right for a different company. Neither has counted the custom programs, the interfaces or the dormant configuration.
The evidence set that replaces opinion is short and concrete:
- A scored inventory of custom code, interfaces, enhancements and reports
- A readiness rating that names the specific blockers
- Effort and cost estimates for each object
- A dependency map showing what breaks when something moves
- A recommended path: brownfield, greenfield or selective
Each item answers a question that workshops cannot. How much of our custom code is still used? Which interface blocks the cutover? What does it cost to fix the ten worst objects? Teams at 2isolutions, a Toronto-based SAP partner working with Canadian clients, build this set before recommending anything.
How Do the Three Paths Actually Differ?
Brownfield converts your existing ECC system in place, greenfield builds a new S/4HANA system from scratch, and selective (sometimes called hybrid) moves chosen processes or company codes while leaving the rest. Each path trades speed, change and risk differently.
Brownfield: convert what you have
Brownfield keeps your configuration, history and custom code. It suits organizations whose processes still fit the business and whose code is mostly clean. The risk sits in the code. Old custom programs that touch removed tables or changed data models will fail, and teams often find that out late.
Greenfield: start clean
Greenfield lets you redesign processes and drop years of accumulated workarounds. However, it also demands the most change management, because users learn new ways of working and finance must decide what history to carry over. It fits companies that have outgrown their ECC design or acquired several divisions with mismatched processes.
Selective: move in parts
Selective paths migrate one company code, a single business unit or a chosen set of data. They fit groups where one entity needs to move now and another cannot. Still, they demand the strictest dependency mapping, since two systems must run side by side and share data.
Why Does the Scored Inventory Come First?
The scored inventory comes first because every later decision depends on knowing what you own. It lists each custom object, rates its usage and complexity, and flags what needs rework. Without it, effort estimates are guesses.
A typical ECC system carries years of custom reports, enhancements and Z programs. Many of them nobody has run in years. A usage-based score separates the live from the dead, and that split changes the economics of the whole project. Code you retire costs nothing to convert.
This is where an SAP custom code assessment earns its fee. It scans your custom objects against S/4HANA simplification rules and tells you which ones will break, which need small edits and which need a rewrite. A related review, the SAP ECC assessment, looks at the wider system: configuration, data volumes, add-ons and modules in use.
Scoring works best when each object receives the same three ratings:
- Business use: is anyone running it, and how often?
- Technical fit: does it comply with S/4HANA rules?
- Fix effort: how many hours to adapt, replace or retire it?
When you total those ratings, patterns appear. A system with a small core of heavily used, easily fixed objects points toward brownfield. Conversely, a system where the heavily used objects are also the badly broken ones points elsewhere. For a broader comparison of the options, this greenfield, brownfield and bluefield overview is a useful companion read.
How Does a Dependency Map Change the Decision?
A dependency map shows which objects, interfaces and data flows rely on each other, so you can see what breaks when one piece changes. It turns a flat list of problems into a sequence of work.
Consider a custom pricing program that feeds a third-party billing tool, which in turn feeds a month-end report the finance team signs off. The program may need only a small fix. But if the billing tool cannot accept the new data format, the small fix becomes a project of its own. The map exposes that chain before you plan around it.
Dependencies also drive the selective path. If one plant’s logistics objects connect tightly to every other plant, carving it out costs far more than the plan assumed. If they stand alone, a phased move works well. You cannot know which case you have by asking people. You find out by tracing the links.
Where blockers hide
Named blockers matter more than general risk scores. A readiness rating that says “medium” helps nobody. One that says “the warehouse interface uses a retired function module and has no documented owner” gives a project manager something to act on. Blockers usually hide in three places: undocumented interfaces, add-ons that lack S/4HANA versions, and data quality problems that only show during load tests.
What Does Effort and Cost Per Object Tell You?
Effort and cost per object tells you which path is cheaper for your system specifically, not for companies in general. When you price each object, you can add up the real cost of conversion and compare it with the cost of rebuilding.
This comparison often overturns assumptions. Teams that expect brownfield to be cheap sometimes find that a handful of heavy objects drive most of the effort. Teams that fear greenfield cost sometimes find that rebuilding is close to the price of fixing a messy estate, and that it delivers a cleaner result.
The numbers also support the less popular outcome. An honest assessment may say that migration is not advised right now. Perhaps the system is stable, the business is about to divest a division, or the code debt is so heavy that fixing it first makes more sense. A report that never says “not yet” is a sales document, not an assessment.
Comparing the paths side by side
With per-object figures in hand, you can build a simple comparison across the three paths:
- Total remediation effort for custom code under each path
- Data migration and cleansing effort
- Business change and training load
- Downtime and cutover risk
- Time to first business benefit
Put numbers beside each line and the debate shifts. Executives stop arguing about philosophy and start arguing about assumptions, which is a far more productive conversation. Teams delivering SAP S/4HANA Implementation work in Canada see this shift in nearly every steering committee that sees real figures.
How Should You Run the Assessment Before Committing?
Run the assessment as a short, structured exercise with a technical analysis phase and an architect review. It should finish before you sign a rollout contract, so the findings shape the contract rather than arrive after it.
A practical sequence looks like this:
- Extract custom code and usage statistics from the ECC system.
- Scan the code against S/4HANA simplification rules.
- Score each object for use, fit and effort.
- Trace dependencies across interfaces, add-ons and data flows.
- Rate readiness and name the blockers.
- Have a senior architect review the findings and recommend a path.
The analysis itself usually takes days, followed by the architect’s review. Production business data is not required, because the scan reads code and system metadata, not customer or financial records. That matters for security teams who would otherwise slow the start.
Many organizations also want to test the result. A fair approach is to compare the findings against a sample of what your system integrator reports. If one assessment flags far fewer problems than another, ask to see the objects behind the numbers. Evidence that anyone can inspect beats confidence that nobody can check.
Keep the findings in a shared workspace that the steering committee, the architects and the finance team can all open. When every group reads the same scores, the same blockers and the same cost lines, disagreements surface early and get settled with facts rather than with seniority. It also gives auditors a clear trail from evidence to decision, which saves hours of explanation months later.
How Does the Path Shape Your Project and Hiring Plan?
The path you pick decides which skills you need and when. Brownfield leans on ABAP developers and technical architects early. Greenfield leans on functional consultants and change leads. Selective needs integration specialists who can keep two systems aligned.
This is where early evidence saves money. If you know the code remediation volume, you can size the developer team before the project starts instead of scrambling mid-way. The same applies to any SAP custom code migration, where the bulk of the work often lands in a short, intense window that demands experienced people.
For consultants, the shift is useful to understand. Demand is strongest for people who can read an assessment, translate it into a plan and defend the estimate. Those who pair ABAP skills with S/4HANA simplification knowledge stand out. Providers of S4hana Services increasingly look for that blend, and candidates who build it find shorter searches.
Planning for the Canadian market
Canadian organizations add a few local factors. Many run bilingual operations, work under provincial and federal data rules, and depend on a smaller pool of senior SAP talent. Working with a provider that offers SAP S4HANA Implementation Canada teams who know these constraints reduces surprises at cutover.
Frequently Asked Questions
Q. How long does an S/4HANA migration assessment take?
A. The technical analysis usually takes days, not months. A senior architect then reviews the findings and confirms the recommended path. The exact timing depends on system size and the number of custom objects.
Q. Do you need production business data to run the assessment?
A. No. The analysis reads custom code, usage statistics and system metadata, not customer or financial records. That keeps the security review short and lets the work start quickly.
Q. What if migration is not the right move?
A. The assessment says so plainly. If the numbers show that code debt, timing or business plans make migration a poor choice now, 2isolutions will report that and explain what to fix first.
Q. Can we compare the result with our system integrator’s assessment?
A. Yes, and you should. Ask each provider to show the objects behind their numbers, and compare them against a sampled set. Differences in scope or scoring usually explain gaps in cost.
Q. Which path suits most companies?
A. There is no default answer. Brownfield suits clean, well-used systems, greenfield suits estates that have outgrown their design, and selective suits groups that must move in parts. Your scored inventory and dependency map decide it.
Let the Evidence Choose, Then Commit With Confidence
Path decisions go wrong when they rest on preference. A scored inventory, a dependency map and per-object costs replace preference with facts, and they give executives something firm to approve. They also allow an honest outcome that opinion rarely permits: not yet, or not this way.
The sequence is simple. Assess the system, name the blockers, price the work, compare the three paths and then choose. Done in that order, the decision holds up under audit, budget review and the first hard week of the project.
Email us at info@2isolutions.com to book an AI environment assessment.
