Data Migration Planning

SEAMAP splits a migration into work packages. What does '19/2' mean, and what does that split tell you about scheduling?

During a system conversion you have an existing sidecar scenario replicating data from several systems into one central system. Why can't it just keep running on S/4HANA?

After the database schema is adapted in a system conversion, how does SAP actually convert your existing data into the current S/4HANA data models — and what changed in 1709 to help?

Conversion runtime in your S/4HANA system conversion is dominated by data volume. What lever should you pull before migrating to shrink it?

Where do you find the authoritative SAP Activate roadmaps, and how are the S/4HANA ones grouped so you pick the right one?

Inside an SAP Activate roadmap, which workstream do the data-migration deliverables actually live in?

What does the prepare phase of data migration actually deliver, beyond 'get ready'?

When several retention systems hold the 'same' data, how does the explore phase decide which one feeds each migration object?

A value mapping recoded every source value 1:1 and passed all syntax checks, yet companies ended up in the wrong country. How does that happen?

You can validate before or after the load. What's SAP's default rule, and when does validating before the migration earn its keep?

Why is the productive load called the most critical phase when, by then, all the 'real' work is supposedly done?

Beyond the data itself, which real-world cut-over details routinely derail a go-live weekend?

You're migrating on S/4HANA Cloud public edition. What platform-driven downtime must your load schedule dodge?

In SEAMAP effort estimation, what are 'general efforts', and what ballpark total should you expect for them?

A client argues that greenfield is the safest choice for their data because everything gets a clean start. What is the actual data benefit of greenfield, and what is the trade-off they are missing?

You are about to prepare source data for the S/4HANA migration cockpit. Where do the templates come from, and why can't you just reuse one template for every object?

What does the mapping phase actually produce — and how is its output different from what the cleansing phase produces?

A teammate says "let's load the data through SEAMAP." Why is that wrong, and what is SEAMAP actually for?

A PM marks data migration "done" the moment the production load finishes at go-live. What two activities does the "productive load and support" phase say still remain?

Someone argues data migration should wait until just before go-live so it runs against frozen config. Why is starting early the cheaper bet?

When planning per migration object, which three attributes must be tracked — and which one, if omitted, breaks your load sequencing?

What makes a productive load test (PLT) different from any earlier test load — and what two things does it actually measure?

Is the S/4HANA data-migration phase model fundamentally SAP-specific, or something else — and why does the answer matter for planning?

What concrete data-migration testing capability does a three-system landscape give that a two-system one does not?

Is data migration a standalone project running alongside SAP Activate, or part of it — and what does the answer change about scheduling?

What is the earliest you should start the data-analysis phase, the latest you can afford to, and why is starting late costly?

Why does data cleansing belong in the source before migration rather than in S/4HANA after the load?

How many phases does SAP differentiate for data migration, and what are they?

Why does picking the correct SAP Activate roadmap matter for data migration, and what distinguishes the available roadmaps?

When does the validation phase run relative to the load, and what does "correctness" cover beyond just record counts?

Data cleaning vs data cleansing — which one enriches data, and why does treating them as synonyms under-scope your migration?

For data cleansing on a migration, should you build a new cleansing team inside the project? What does SAP recommend instead, and why?

Why does data mapping realistically slip into the realize phase instead of finishing in prepare — and what should the plan assume because of it?

Beyond object type and complexity, what else must a SEAMAP migration-object inventory record — and which omission most directly underestimates load effort?

Across which SAP Activate phases does data cleansing actually run, and why isn't it a one-time task you finish in prepare?

When you need to cleanse and raise the quality of source data for a migration, which SAP tool is for that — and why isn't it the migration cockpit?

By when must data cleansing ideally be complete, and what goes wrong if you let the PLT run on uncleansed data?

What is "paper mapping," when in SAP Activate does it happen, and why do it before building the real mapping rather than after?

Your migration loads without errors, yet the business finds wrong values in production. Which SAP tools validate migrated data, and what must the validation rules be derived from so they actually catch this?

After you load data into the migration cockpit in the realize phase, what steps still stand between the staged data and the actual migration?

What does 'cut-over preparation' produce that the actual load depends on — and which decision, if left open, stalls the go-live?

During production cut-over in the deploy phase, some master data isn't loaded by tools at all. What must you explicitly verify because of that?

You're staffing a data-migration project team and want the two SAP trainings that cover the platform they'll run on and the methodology they'll deliver in. Which two, and what does each one target?

In the on-premise (Business Suite – Agile and Waterfall) roadmap, what does the prepare phase do before any strategy document is finalized?

The on-premise explore phase adds a data-migration deliverable that the cloud roadmaps largely don't emphasize. What is it?

Before optimizing load performance, what's the single highest-leverage thing you can do to shorten total import time?

The migration cockpit and Rapid Data Migration both ship predefined objects — but what technical interface underlies each, and why does that matter?

What does the implementation phase build, and why do you have less freedom to hand-roll it on S/4HANA Cloud public edition?

Before you wire up a BAPI, IDoc, or batch input for migration, what must you confirm — and what happens if you skip the check?

Across which SAP Activate span does the test phase run, and why does the book call testing the most-neglected success factor?

During test loads you keep reloading transaction data and wish you didn't have to reload master data each time. What technique fixes that?

Your source files carry units of measure in local/commercial forms, but the migration API rejects them. What conversion does SAP require, and what do you do for a unit with no official ISO code?

Why can tool selection (SEAMAP WP20) blow your timeline in a public-sector project specifically?

When you tally up where migration time goes, which single activity should dominate — and by roughly how much?

You tested the migration by loading a few sample records and they worked. Why is that not the test SEAMAP WP15 means?

Why does a public-cloud S/4HANA migration typically run fewer SEAMAP work packages than an on-premise one?

How is the SEAMAP effort-estimation spreadsheet structured, and what does its info area capture per migration object?

Which SEAMAP work packages scale with the number of migration objects rather than being one-off, and why does that distinction matter for estimating?

Where do you get the authoritative, current list of available migration objects — and general data-migration guidance — for your specific S/4HANA product?

In the cockpit's new-implementation transfer flow, in what form is cleansed source data handed over, and where are basic inconsistencies caught?

Why does SAP tell you to run a sizing report in your existing SAP ERP system rather than size the new S/4HANA box from generic rules?

In a greenfield new implementation, which data actually comes across from the old ERP — and why is dragging historical data over a bad default?

You're consolidating several ERP systems via a new implementation. How does the data scope differ from a single-system greenfield?

You want to move financial planning and consolidation from a separate SAP BPC system into S/4HANA early. Why can't that happen until the end?

Explore-phase cleansing isn't only about fixing bad values. What does it do about data that simply shouldn't come across at all?

A colleague uses 'business object' and 'migration object' interchangeably. Why is that wrong, and when does one business object need several migration objects?

Why does the master-vs-transaction data distinction drive your migration approach, not just your vocabulary?

For a handful of records, when is building automated conversion logic the wrong call?

You've crossed from planning into the on-premise realize phase — what is the one thing you now actually build for data migration, rather than just plan?

Populating a public-cloud QA system with realistic test data used to be a blocker. What service solved it, and what's the GDPR catch?

Completed financial documents usually can't be migrated in a new implementation. What's the sanctioned way to bring their balances, and since when?

If the business genuinely needs access to historical data you can't migrate, what three architectural options does SAP suggest?

In SEAMAP's data-analysis phase, which four work packages run, and how do you pick the 'leading' source system?

For fields that have a conversion rule, what extra check does the cockpit run — and what must you remember to switch on for custom migration objects?

Before the cut-over, SAP recommends simulating the go-live several times rather than once. What does a single successful rehearsal fail to prove?