If your ECC system runs OpenText Vendor Invoice Management, your move to SAP S/4HANA has an invoice project inside it, whether or not anyone wrote it down. The archive behind VIM comes along too. Both belong in scope before the cutover plan is written, not on the weekend it runs.
Six weeks or five days
A client's S/4HANA go-live was called off because VIM hadn't been accounted for in the conversion scope. The implementation partner estimated six weeks to fix it. The client called us after the go-live was abandoned, and we resolved it in five days.
The gap wasn't about working faster. It came from already knowing where VIM sits in an SAP landscape and what a conversion does to it. The five-day fix was three pieces of work:
- Capture. The client's capture setup came from an older generation that VIM 25.4 no longer supports, so capture moved to Core Capture, with the old OCR profiles carried over.
- VIM configuration. VIM's BC Set content for the 25.4 release had to be reviewed and activated, and customizations that had been overwritten had to be restored.
- The archive path. In development, the content server had never been configured, so invoice images wouldn't display until that path was set up.
None of it was exotic. Every item was ordinary VIM and archive work that fits easily into a project plan when someone owns it from the start.
Why VIM falls through the gaps
VIM is installed as add-ons inside the SAP system, so SAP's conversion tooling does see it. SAP's conversion guide says the Maintenance Planner checks installed add-ons and prevents the conversion when one has no valid conversion path. That covers the ABAP layer. It doesn't tell anyone who runs the capture servers, which Validation Client release the AP team uses, or where the invoice images actually live.
Those pieces have their own rules. An SAP product expert's VIM upgrade checklist on SAP Community makes the main ones plain: the VIM target release follows the S/4HANA target release (it cites SAP Note 3654390 for S/4HANA 2025 needing VIM 25.4), VIM 25.4 no longer supports Business Center Capture or Invoice Capture Center components, and VIM doesn't store the document at all. The archive repository does, linked to the SAP record through ArchiveLink.
Archiving has a second job in a migration. OpenText's S/4HANA migration guidance is to archive inactive SAP data before the move, which shrinks both the database and the migration scope, and to set classification and retention rules during migration prep rather than retrofitting them after go-live.
What to put in scope before cutover
- An inventory with owners. The VIM release and add-ons installed today (Foundation, Invoice Solution, Fiori UI, any optional scenarios), with a named owner on the project plan.
- The VIM target release. Decide it from the S/4HANA target release, not on its own.
- Capture. What runs today, whether it is supported on the target VIM release, and where it lands: on-premise Capture for SAP Solutions or cloud-based Core Capture. Keep validation on the same release level as VIM and capture, or plan the move to Fiori validation.
- The archive path in every system. Which repository holds invoice images, and whether the ArchiveLink content repositories and document types are set up in development and QA as well as production. Open an invoice image from the new system before anyone calls testing done. Our post on ArchiveLink document types before go-live goes deeper.
- What to archive before the move. Agree which ECC data and documents get archived first, and who sets the retention rules for them.
- Integrations. Email, scan, IDoc, Ariba or other inbound channels that must still work on day one.
- VIM lines in the cutover runbook. Transport order, invoices still in workflow at cutover, and one invoice traced end to end in production after go-live.
- AP in user testing. The people who process invoices test the new system, not only the project team.
If that list takes ten minutes to fill in, good. If it starts a long conversation, it's a conversation worth having while the plan is still a plan. Our S/4HANA preparation questions cover the release and maintenance side.