A 3–5 week structured discovery that quantifies HANA data volumes, ABAP/CDS customisation inventory, integration surface, and sized migration plan with timeline and budget envelopes. Answers the seven questions your executive sponsor needs before approving the migration spend.
Skipping the assessment is the single most reliable predictor of a multi-million-pound migration slip.
S/4HANA migration projects fail in characteristically predictable ways: customisation complexity is discovered in week 14 not week 4; integration touchpoints with unknown downstream consumers are discovered in cutover-rehearsal not in planning; HANA data volumes that drive multi-week extraction windows are discovered when extraction starts, not when scope is fixed. Each of these failures is preventable — but only if discovery happens before scope is fixed, not after.
Syntra ETL's S/4HANA migration assessment exists to turn discovery into a 3–5 week structured exercise with defensible outputs. The assessment uses automated discovery against your S/4HANA system (HANA SQL or CDS view access for data-volume profiling, ABAP repository crawl for customisation inventory, SAP Gateway and CI tenant introspection for integration discovery) combined with structured functional interviews. The output is not a vendor PowerPoint — it's a numbered, evidenced, sized migration plan with timeline, resource profile, budget envelope, and risk register.
Critically, the assessment is bundled with the migration on commitment. Customers who proceed with Syntra ETL's full migration get the assessment cost credited against the migration fee — net cost of the assessment is zero. Customers who use the assessment to test the waters and don't proceed pay the standalone fee, but typically extract immediate value from the data-volume and customisation insights regardless. Either way, the £35K–£90K assessment cost is a tiny fraction of the £1M–£5M-and-up cost of a slipped migration.
An executive sponsor approving a multi-million-pound SAP migration needs these seven answers with evidence, not vendor handwaving.
Sized timeline, FTE profile, budget envelope with confidence interval — defensible against vendor lowballing and SI doubling-down. Typical multi-pillar Fusion migration: 14–22 weeks, £1.5M–£4M envelope.
Every Z-report, CDS extension, BAdI counted and classified. Typical: 35–55% retired outright, 20–30% replaced with Fusion native, 15–25% need VBCS/OIC rebuild, 5–15% are strategic and need careful equivalents.
Every IDoc partner, BAPI consumer, OData service mapped to upstream/downstream system. Surprise dependencies — the legacy app whose owner left two years ago — surfaced in discovery, not in cutover.
Per-domain split of what lands in Fusion vs what routes to compliance archive. Typical: 20% of HANA data into Fusion (open and recent), 80% to archive. Saves Fusion storage cost; preserves HGB/SOX/FDA retention.
Quantified licence release at decommission: HANA Enterprise per-GB licence, S/4HANA application licence, RISE subscription if applicable. Typical mid-large: £1M–£5M+/year recoverable.
Per-regime coverage: German HGB §257/§147 10y, SOX 7y, BaFin sector-specific, FDA Part 11 full-lifecycle, GDPR Article 25. Compliance archive design covering every applicable regime.
A repeatable, automated-where-possible workflow. Outputs are numerical and evidenced, not narrative.
Read-only access provisioned: HANA DB user (where direct access available), CDS view consumer role (where access is mediated), ABAP repository read access, SAP Gateway log access, SAP CI/PI/PO tenant introspection. Sample auth profiles documented.
Automated scan: row count and HANA in-memory size per ACDOCA, BKPF/BSEG, KNA1/LFA1, MARA/MARC, EKKO/EKPO, asset register, payroll cluster, per BUKRS, per fiscal year. Growth rates calculated over last 3 years. Heat-map produced.
TRDIR/TADIR/DDLDEPENDENCY/V_EXIT_ACT crawled. Every Z-report, CDS extension, BAdI, IDoc partner, ABAP CAP service catalogued with last-modified date and execution frequency (from STAD/ST03 statistics).
IDoc partner profiles, BAPI consumers, OData consumers, SAP CI/PI/PO interface inventory captured. Upstream/downstream system identification via header inspection and functional confirmation.
Structured interviews with finance, SCM, HR (if SAP HCM present), tax, audit, security. Validate automated discovery against actual usage. Identify pain points motivating migration. Capture risk flags.
Sized migration plan: timeline, FTE profile, budget envelope, risk register, per-domain archival strategy, compliance coverage matrix, year-one TCO saving forecast. Executive briefing pack and detailed appendix delivered.
A standardised set of artifacts that has been refined across dozens of S/4HANA assessments. Not bespoke; not vendor-marketing.
20-slide deck with the seven executive-question answers, sized headline numbers, risk-register summary, and recommended next steps. Designed for board / steering-committee presentation.
Per-table HANA in-memory size with growth projection. Drives extraction-parallelism sizing for migration and archival-strategy split between Fusion-loaded and archive-routed data.
Every Z-report, CDS extension, BAdI, IDoc partner, CAP service catalogued. Classified retire / Fusion-native / VBCS / OIC / BI Publisher with effort estimate. Drives the technical-redesign workstream.
Every IDoc, BAPI, OData, CI/PI/PO touchpoint mapped to upstream/downstream system. Disruption-risk scored. Drives the integration-disconnection workstream.
Per-regime (HGB, SOX, BaFin, FDA, GDPR) coverage of archival design and migration plan. Validated with DPO and compliance leads pre-delivery.
Year-one and 5-year TCO comparison: stay on S/4HANA vs migrate to Fusion + decommission. HANA licence, RISE subscription, infrastructure, support, archival cost, Fusion subscription all modelled.
An SAP S/4HANA migration assessment is the discovery and scoping phase that quantifies what's actually in your S/4HANA system before you commit to a migration timeline and budget. The assessment outputs four artifacts: a data-volume map (HANA in-memory footprint per table, per company code, per fiscal year, with growth-rate projection), a customisation inventory (every ABAP Z-report, CDS view extension, BAdI implementation, IDoc partner profile, ABAP CAP service — classified by business purpose), an integration-surface map (every IDoc partner, BAPI consumer, OData service, SAP CI tenant — with upstream and downstream system identification), and a sized migration plan (timeline, resource profile, budget envelope, risk register). Without an assessment, S/4HANA migration projects routinely slip 2-3x past initial estimates because critical complexity was discovered only during execution.
Typically 3–5 weeks from kickoff to deliverable sign-off, depending on landscape complexity. Single-instance, single-country, mid-size S/4HANA: 3 weeks. Multi-instance (production + non-production), multi-country, with RISE with SAP and on-prem mix: 5 weeks. The first week is discovery setup (HANA read access, CDS catalog access, ABAP repository access). Weeks 2–3 are automated scanning: data-volume profiling, customisation inventory crawl, integration discovery via PI/PO/SAP CI tenant introspection. Week 4 is functional review (interview finance, SCM, HR leads about their actual usage and pain points). Week 5 is synthesis — turning raw discovery output into a sized, defensible migration plan with cost and timeline envelopes. Compare this to traditional consultant-led discovery (3–6 months) for the same depth.
Volumes per table per BUKRS per fiscal year. ACDOCA row count and HANA in-memory size, growth rate over last 3 years. BKPF/BSEG legacy journal volumes (for ECC-heritage customers). KNA1/LFA1 vendor and customer master sizes, with growth and turnover rates. MARA/MARC material master across all plants. EKKO/EKPO purchase-order volumes. VBAK/VBAP sales-order volumes. Asset register (ANLA/ANLB/ANLC) per book and depreciation area. Payroll cluster (PCL2) size where SAP HCM is present. Output is a heat-map of which tables drive HANA in-memory cost, which carry archival opportunity, and which need the heaviest extraction parallelism during migration.
Discovery engine crawls TRDIR (ABAP repository), TADIR (development objects), DDLDEPENDENCY (CDS view extensions), V_EXIT_ACT (BAdI implementations), modification adjustment tables (SMODILOG), IDoc partner directory (EDPP1/EDPP2), and SAP CAP service catalog. Output is a complete inventory: every Z-report with last-modified date and execution frequency, every CDS view extension with consumer list, every BAdI implementation with enhancement-spot context, every IDoc partner with EDI message type. Each artifact is classified by business purpose (best-effort, with functional review confirming): retire (35–55% typical), replace with Fusion native, replace with VBCS extension, replace with OIC flow, replace with BI Publisher. The classification drives migration-effort sizing — the cost of moving 200 Z-reports is fundamentally different from the cost of moving 30 strategic ones.
Yes — comprehensively. Integration discovery covers: IDoc partner profiles (WE20/WE21 configuration, message-type traffic from EDPP1/EDPP2), BAPI consumer identification (SAP Gateway logs, RFC callers), OData service consumers (SAP Gateway service activations, log analysis), SAP PI/PO/CI tenant introspection (interface and channel inventory), and BTP integration suite (where applicable). Each integration is mapped to its purpose: B2B EDI with named trading partners, internal app-to-app integration with named systems, real-time order/inventory sync with e-commerce, regulator reporting feeds. The output drives the integration-disconnection workstream during migration and decommissioning.
Standalone assessment pricing typically £35K–£90K depending on landscape size and complexity. Bundled with full Syntra ETL migration: assessment cost is credited 100% against the migration fee on contract signature, so customers who proceed with migration effectively get the assessment free. Customers who use the assessment to test the waters (run it standalone, then either proceed with migration or shelve the initiative) pay the standalone fee. Even shelved-initiative customers regularly find the assessment delivers immediate value — actionable HANA data-volume insights that drive immediate licence renegotiation or archival quick wins worth multiples of the assessment cost.
Yes. For customers weighing strategic options ('do we stay on-prem S/4HANA, move to RISE, or migrate to Oracle Fusion?'), the assessment can include a 3-way TCO and risk comparison. Inputs: current on-prem licence and infrastructure run-rate, vendor RISE quote (if available), Syntra ETL Fusion migration estimate. Outputs: 5-year TCO per option, risk profile per option (vendor lock-in, HANA licence escalation, integration disruption, organisational change), strategic-fit assessment per option (do you want SAP innovation, or Oracle innovation, or single-vendor consolidation?). Customers find this comparison useful for board-level decisions even when the eventual choice is to stay on S/4HANA — the analysis surfaces optimisation opportunities regardless of strategic direction.
Seven concrete answers an executive sponsor needs before approving a multi-million-pound migration. (1) How big is the project actually — months, FTEs, budget envelope? (2) What does the customisation profile look like — and how much of it survives in Fusion vs has to be retired/rebuilt? (3) Where are the integration disruption risks — which upstream/downstream systems break if SAP goes away? (4) What's the cleanest archival strategy — what stays on Fusion, what goes to compliance archive? (5) What's the realistic HANA licence saving in year one of decommissioning? (6) What's the regulatory compliance posture — German HGB, SOX, BaFin, FDA all covered? (7) What's the rollback strategy if Fusion isn't ready? The assessment deliverable answers all seven with defensible numbers, not vendor-marketing handwaving.
30-minute scoping call. We'll confirm landscape complexity, discovery-access feasibility, and assessment duration — and book the kickoff. Assessment cost credits 100% against any subsequent Syntra ETL Fusion migration.