Domino-to-S/4HANA Data Migration

Our organisation is retiring several HCL Domino databases and consolidating everything inside SAP S/4HANA. The task centres on a one-time, batch-style migration that moves three critical data sets—customer, financial and inventory records—into their new homes in S/4HANA without data loss or functional gaps.

What this involves
The Domino data model must be mapped to the relevant SAP tables, transformed where needed (currency, units of measure, IDs, date formats, etc.) and then loaded through a controlled batch process. After load, a reconciliation step must confirm record counts and key totals so our finance and operations teams can sign off with confidence.

Key considerations
• Source: HCL Domino (Notes NSF files; views and agents available)
• Target: SAP S/4HANA 2022 (on-premise)
• Preferred flow: Design, mock migration in a sandbox, final production cut-over during a weekend window
• Typical tooling expected: SAP Data Services, SAP LT, IDoc/BAPI calls or comparable ETL utilities—open to whichever stack completes the job reliably and audibly

Deliverables
1. Field-level mapping and transformation document
2. Reusable ETL jobs/scripts and any supporting code
3. Test migration results with reconciliation report
4. Final production migration with post-load validation report
5. Handover guide so our internal team can audit or rerun the process if required

Acceptance criteria
• 100 % of source records present in the target tables
• Financial balances and inventory quantities match legacy totals to the cent/unit
• No critical SAP run-time errors after migration (idoc, posting, stock)
• Sign-off from finance and supply-chain leads

Timing is flexible within the next month, provided the cut-over can occur across a single weekend. Clear communication and thorough documentation are just as important to us as the technical work itself.