Linos Migrate.
End-to-end ECC → S/4HANA in one cockpit.
An 18-month brownfield program runs on spreadsheets, SharePoint, and a thousand emails today. Linos Migrate replaces that with a single source of truth: the 5-phase framework as a state machine, the eight critical workstreams as live modules, AI advisory wired into every decision, and reconciliation evidence at every gate.
Brownfield programs slip on the same five things.
Two decades of SAP work, every brownfield engagement runs into the same gaps. They’re not technical — they’re program-management.
Pre-check fatigue
SAP Readiness Check produces hundreds of items. Without a single backlog with owners, severities, and statuses, critical items rot in spreadsheets. Programs hit DMO with unresolved CVI gaps and unfixed Z-code.
Custom code paralysis
ATC findings without SCMON usage data is a wall of red. Teams remediate the loud objects and miss the high-traffic ones. Decommission candidates linger and get migrated unnecessarily.
FINS_MIG mystery
The four-step finance cockpit is irreversible at step 4. Without a clear ordering, evidence of pre-checks, and reconciliation gates, finance teams refuse to sign go/no-go. The program stalls.
Reconciliation theatre
Spot-checks on a few G/L accounts get presented as 'reconciled.' Real line-by-line comparison ECC ↔ S/4 with tolerance thresholds rarely happens until cutover weekend, when it's too late.
Cutover chaos
A 72-hour runbook with 50+ steps, executed across five teams in three timezones, on a Saturday. With no live status, no go/no-go gates, no escalation path — one missed step takes the cutover sideways.
Lost institutional memory
When the project ends, the lessons live in 12 binders nobody opens. The next ECC → S/4 customer pays for the same mistakes again. Linos Migrate is built to capture all of it.
Five phases. Hard gates between each.
Linos Migrate is opinionated about the brownfield framework: five phases in strict order, each with explicit gates. A phase only advances when its blocking pre-checks are cleared, all tasks are done, and a human approver signs.
- Zero HIGH or CRITICAL pre-checks open before DMO
- CVI / Business Partner synchronization at ≥ 99% before DMO
- FINS_MIG steps 1–3 = PASSED before VALIDATION
- FINS_MIG step 4 (activation) explicitly flagged as IRREVERSIBLE — separate sign-off required
- Every gate transition recorded in immutable audit log with actor, timestamp, and approver
Eight modules. One cockpit.
Each module owns one workstream end-to-end: pulls data from ECC and S/4 via the connector layer, persists state, exposes a UI, and feeds the AI advisor.
Pre-Check
Aggregates SAP Readiness Check + Simplification Items into a single backlog with severity, owner, status, and remediation. Hard gate: zero CRITICAL items unresolved before DMO.
Custom Code
Combines ATC findings with SCMON usage (last 12 months calls). Auto-prioritized by severity × usage. Effort estimates per object. Quick-Fix flagging. Unused Z-objects auto-marked for decommission.
CVI / BP
Customer/Vendor → Business Partner synchronization tracked in source ECC. Grouping and number-range issues surfaced. ≥99% sync enforced as a hard gate before DMO.
DMO Runs
Each Software Update Manager rehearsal logged across the landscape, with R3load process count, uptime/downtime split, completion time, and error notes.
FINS_MIG
The four-step finance migration cockpit. Strict ordering: step N requires step N-1 = PASSED. Step 4 (activation) is explicitly flagged as IRREVERSIBLE.
Reconciliation
GL, AA, MM, AR/AP, ML balance comparison. Per-line ECC ↔ S/4 with tolerance threshold. Out-of-tolerance lines escalated for investigation.
Cutover Runbook
Standard 13-event cutover template with timestamps, owners, and explicit go/no-go gates. Status transitions logged with actual start/end times.
AI Advisor
Claude Opus 4.7 reads live state across all modules. Modes: risk analysis, runbook generation, error triage, executive briefing, ABAP remediation drafts.
Claude reads live state. Acts as a senior PMO advisor.
The AI advisor pulls the project state across every module — pre-checks, custom code findings, CVI sync, DMO runs, FINS_MIG, reconciliation, cutover — and feeds it as structured context to Claude Opus 4.7. No copy-pasting, no model bolted on the side.
Risk heatmap
Per-workstream risk score on impact × likelihood, refreshed on demand. Drill into the underlying findings driving each red square.
Executive briefing
One-click weekly status digest for the steering committee: top risks, what shipped, what's blocked, decisions needed. Markdown out, copy-to-Slack.
ABAP remediation drafts
On each custom code finding, ask Claude for a specific code change. Reads the ATC text, the simplification SAP Note, and the SCMON usage to propose the fix.
Runbook generation
Generate cutover runbooks tailored to your landscape — on-prem, RISE, hyperscaler. Adjusts for downtime tolerance and team timezones.
Reconciliation triage
When ECC ↔ S/4 balances differ beyond tolerance, Claude inspects the period, account, and posting logic to suggest the most likely cause (rounding · timing · unposted documents · CO settlement).
Error triage
Paste a SUM/DMO error or FINS_MIG dump. Claude pulls the relevant SAP Note, identifies the failure class, suggests next steps.
Pluggable. Mock for evals, RFC or OData for production.
The connector interface abstracts SOURCE_ECC and TARGET_S4 access. Swap implementations via a single environment variable. Mock is the default — no SAP system required to demo.
Mock connector
Deterministic synthetic data. Demos, evals, dev work — no SAP needed. Default mode out of the box.
RFC connector
BAPIs and function modules via SAP NW RFC SDK + node-rfc binding. Reads ATC, SCMON, CVI, FINS_MIG cockpit, GL balances directly from ECC and S/4.
OData connector
REST/OData v4 calls to SAP Gateway. Useful for cloud-only S/4HANA where RFC isn't preferred. OAuth2 client credentials or basic.
SaaS today. Fiori extension when you need it.
Same backend domain logic and TypeScript types power both deployment modes. The frontend is interchangeable; the connector layer is pluggable.
Standalone SaaS
Docker container on a DigitalOcean Droplet (or AWS / Azure / GCP). Caddy auto-TLS, SQLite or managed Postgres. Multi-tenant or per-customer.
https://migrate.linosconsulting.com →Fiori extension on BTP
Same backend domain logic lifted into SAP CAP (@sap/cds). React UI replaced with SAPUI5. Embedded in the customer's Fiori Launchpad with XSUAA SSO and Cloud Connector reach-back to ECC.
Walk through the cockpit on a sample brownfield project.
Request an evaluation tenant and we’ll seed it with a realistic Acme Corp ECC 6.0 → S/4HANA 2023 program — 7 readiness items (4 critical), 10 ATC findings, 24 CVI records (~70% synced), 3 DMO rehearsals, the FINS_MIG cockpit, and the standard 13-event cutover runbook. You’ll be able to advance the phase engine and ask the AI advisor questions in your own sandbox.