Welcome to this second edition of /n Procurement.
Last month I laid out why SAP is building next-gen Ariba, and the basics behind the “what”. This month is about the toll gate standing between you and all of it.
Your SAP Business Network account has to be migrated to SAP’s Business Technology Platform (BTP) before you can do anything in next-gen Ariba. Every account has to move by the end of 2026 in waves SAP assigns (buyers and suppliers). You don’t apply, and you don’t pick your slot. SAP is managing it end to end, as turnkey as they can make it.
The promise? Nothing breaks. Nothing new starts either.
That combination is what makes this one easy to ignore. The 30-day notice lands in a shared inbox, nothing is on fire, no process changes… So nobody picks it up. Then the interface changes on a Tuesday and your category managers are fielding supplier questions nobody briefed them for.
There’s also a twist worth sitting with. SAP sequences the waves by complexity, so the organizations running the most network functionality go last. The teams most invested in the network are the ones waiting longest for what comes next.
Let's get into it.
📢 What you'll find in this edition:
🔗 Worth Bookmarking
🔁 SAP Business Network Migration to BTP: What Changes in 2026
🔵 Best LinkedIn Post of the Month
💬 Worth Repeating…
🌯 Wrap Up
Note: Some of the content listed above is only available in the email version of this newsletter. Don’t miss out! Sign up for free to get the next edition.
The Monthly Update
SAP Business Network Migration to BTP: What Changes in 2026
As mentioned in the last edition, one of the key prerequisites for SAP customers before moving to the Next-Gen SAP Ariba platform is to migrate your SAP Business Network to SAP's Business Technology Platform (BTP) first.
Since we're talking about the SAP Business Network, this migration impacts both buyers (your company) and suppliers you're doing business with over the network. This article lays out the changes and updates for both parties.
📌 SAP BTP (Business Technology Platform): SAP's cloud platform. The shared foundation of hosting, data management, identity, integration, and AI services that SAP builds and runs its own applications on.
Moving the Business Network "to BTP" means rehosting it on that common platform instead of the standalone infrastructure it has lived on for 25 years.
First, a Quick Refresher on the Ariba Architecture
If you sit on the procurement side, it is worth restating how the pieces fit together, because the architecture explains why this migration has to happen in the order SAP has chosen.
The Ariba modules are customer-facing only. Ariba Sourcing, Contracts, Buying and Invoicing, Supplier Lifecycle and Performance, and Spend Analysis are where your category managers, contract owners, requisitioners, and AP team do their work. Your suppliers do not log into them.
SAP Business Network is the application layer that brings suppliers into those processes. SAP Business Network (the artist formerly known as the Ariba Network 😅) is where a supplier theoretically keeps a single account, and it is the layer through which they respond to sourcing events, collaborate on catalogs and contracts, receive purchase orders, flip them into invoices, confirm schedules through supply chain collaboration, and complete registration and qualification questionnaires.
One supplier account can serve many buyers, and one buyer can reach millions of suppliers through the network. That many-to-many relationship only works because the network sits between them as a shared layer rather than as an extension of any one customer's modules.
📌Editor’s Note: SAP Business Network isn’t just a rebrand of the Ariba Network, it’s also a regrouping of all of the existing “SAP network” solutions into a single technology stack.
In addition to the Ariba Network and Supply Chain Collaboration, SAP Asset Intelligence Network and the SAP Logistics Business Network are also being folded into the unified SAP Business Network.
Everything else plugs into the business network layer. Your modules are only as capable as the network they transact through because lots of your processes involve suppliers... Similarly, if suppliers are sending you electronic transactions (e.g. EDI or cXML purchase orders) through the network. The network piping needs to be solid.
That is why SAP is moving the Business Network to BTP first and the Ariba modules afterward: the shared foundation everyone transacts through has to move before the customer-facing applications that sit on top of it can follow.
Why Is SAP Migrating the Business Network to BTP?
SAP Business Network is more than 25 years old as an application, and its underlying architecture has remained largely unchanged over this time. It has historically been a single, monolithic application hosted entirely in a specific data center in the USA.
Every time a buyer or supplier joins the network, their account information, master data, and transactions are stored on servers based in that data center. For context, the business network currently hosts over 6 million historical registered supplier records, facilitates over $6.5 trillion USD in annual B2B commerce spend, and has committed to supporting ever-growing e-invoicing mandates in more than 40 countries.
The current architecture has outgrown its useful life and cannot remain the same if SAP is to fulfill promises to customers without disruption. Furthermore, customer data sovereignty demands in the "age of AI" are forcing SAP to expand support globally across data centers, giving customers and suppliers the choice of where their data is stored.
The pace of innovation and delivery of new features on the network has been lagging behind SAP's other core offerings, and user experience parity can no longer be ignored. Upgrading the runtime layer to SAP Business Technology Platform (SAP BTP) allows SAP to address these challenges.
📌 Runtime Layer: the technology supporting the period when a program is actively running and performing operations. It is the moment code moves from instructions written in files to actual behavior carried out in memory, including calculations, user interface updates, network calls, database queries, and everything in between.
This visual captures the core benefits SAP is promising over time as part of this migration to BTP
According to SAP, this is primarily an architectural and user experience upgrade, with little to no change to features and functions. Buyers and suppliers on the network should not be concerned about their processes breaking because of this upgrade. Their configurations, by and large, will remain untouched and as-is.
How BTP migration affects suppliers, and what to do about it?
SAP is rolling out the new interface throughout 2026.
Greenfield Suppliers: New supplier accounts are already on the new user interface. If you are a new walk-up or invited supplier, you have most likely been working in the Next-Gen SAP Business Network environment since December 2025, from the moment you completed your account creation. You should also be able to choose your data center during the account creation process.
📌Walk-up suppliers are suppliers who come to the network on their own to register, without being explicitly invited by any buyer.
📌Invited suppliers are suppliers who are invited by a buyer to create an account in SAP Business Network as part of a purchase-to-invoice process, sourcing event, or supplier onboarding process.
Brownfield Suppliers: For existing suppliers, your timeline depends on your account type: Standard, Enterprise, or Integrated.
📌 Standard, Enterprise, and Integrated accounts: the supplier account types in the SAP Business Network.
A standard account is free and largely email-driven: the supplier can receive orders, flip them into invoices, and track payment status, with limited functionality beyond that.
An enterprise account is a subscription. Fees scale with the volume and value of documents transacted and unlocks catalogs, reporting, a multi-customer dashboard, and priority support.
An Integrated account describes an enterprise account whose ERP is wired directly into the network over cXML or EDI, so documents flow system to system rather than only through the supplier portal (where suppliers need to log in to see transactions).
SAP's own breakdown of the account types is here.
When it is a supplier’s turn to migrate, they will receive a 30-day notice with everything they need to know. Data, connections, and transaction history all move with them. For most suppliers, the change is minimal.
Email Notification: Look for "Supplier Network Account Upgrade Notification" in your inbox. Suppliers using Supply Chain Collaboration functionality will migrate on a separate, later schedule (to be announced).
📌 Supply Chain Collaboration (SCC): the part of the network that reaches past purchase orders and invoices into direct-materials collaboration (e.g. forecasts, scheduling agreements, subcontracting, consignment, quality, and inventory visibility with manufacturing suppliers).
It is the heaviest use anyone makes of the network, which is why it migrates on its own schedule.
This visual outlines when a supplier will see the new next-gen SAP Business Network user interface:
Important: Supplier data is preserved.
Your data, account, and connections are all preserved. Transaction history, account settings, and integrations move with you automatically. Nothing is deleted.
Suppliers can be confident that this transition does not affect the foundation of their account. The following remain fully intact:
Account type: Free or Paid
Pricing model
Existing customer relationships
User access, documents, and historical data
Supplier configuration
Capabilities such as PO flip, catalog uploads, and integrations
One small note: you may need to reset some filters or tiles after the migration.
But, as of now, no action is required from suppliers ahead of their migration date.
Here's the link to a set of tutorials (in English) for suppliers experiencing SAP Business Network on BTP.
How this BTP migration affects buyers (customers), and what to do about it?
What Changes for Buyers
The SAP Business Network buyer interface is being refreshed as part of SAP's broader vision for a more intelligent, resilient, and adaptable business network. The look and feel will change, but the existing functionality remains unchanged.
How Buyer Migration Is Scheduled
SAP schedules each buyer account migration as part of a planned wave. Wave placement is based on deployed features, current configurations, and usage patterns. There is no application or sign-up process; SAP determines your wave placement and notifies you with your timeline and next steps at least 30 days before your migration date.
SAP's goal is to migrate all customers by the end of 2026. If your organization uses Supply Chain Collaboration functionality, your wave is expected to begin in the second half of 2026.
Why Staying on Schedule Matters
There are a few practical reasons to stay aligned with SAP's migration schedule:
The legacy platform will eventually be retired. SAP has not announced an exact sunset date, but the migration is mandatory for all customers.
New capabilities will be delivered only on the new platform. This includes AI agents, advanced analytics, and future innovation that will not be available to accounts that have not migrated.
The migration is a prerequisite for future next-gen SAP Ariba upgrades. SAP Business Network on BTP is required before customers can move to future SAP Next-Gen Ariba procurement applications on BTP.
SAP Ariba applications/modules (Sourcing, Contracts, Buying and Invoicing, etc.) follow a separate migration timeline, but integrations and configurations between SAP Business Network and SAP Ariba applications need to be upgraded first and remain intact through this transition.
If You Need to Request a Delay
If your organization needs more time for whatever reason, raise a ticket through SAP for Me after you receive SAP's initial migration proposal. Clearly explain the reason for the request and include the following details:
Your currently scheduled migration date
The business reason for requesting a delay
Your proposed new timeframe within 2026
SAP will review the request and accommodate it where possible.
📌 SAP for Me: SAP's customer portal and the single front door for anything you need from SAP directly (e.g. support tickets, system and license information, and case history).
It is where this request goes; your Ariba Customer Success team will already have access.
You can log in here.
What Carries Over During Buyer (Customer) Migration
The buyer migration is not a reimplementation. SAP expects no data loss and no anticipated downtime. The following account data, configurations, and relationships are preserved automatically when your account moves to the new platform:
Transaction history and documents: Historical purchase orders, invoices, ship notices, and related documents move with your account. Nothing is deleted.
Catalogs and integration profiles: Catalog configurations and supplier integration profiles carry over intact.
Business rules and configurations: Transaction rules, notification settings, and account configurations are preserved.
User access and roles: User accounts, permissions, and role assignments migrate together.
Child accounts: Child accounts migrate alongside their parent account, with no separate action required.
SAP Ariba application integrations: Existing integrations and configurations between SAP Business Network and SAP Ariba applications remain intact. SAP Ariba applications follow a separate migration timeline.
📌 Child accounts: Additional network accounts that sit underneath a “parent account”, typically used when a company has several legal entities, divisions, or regions that transact separately but need to be administered in one place.
Each child has its own network ID; the parent is where hierarchy, users, and reporting are managed across them.
If you’ve never heard about this and have a fairly simple Ariba setup, it’s probably not relevant for you.
If Your Organization Uses Managed Gateway for Spend & Network
Managed Gateway for Spend & Network (the artist formerly known as Cloud Integration Gateway or CIG 😅), does not require manual endpoint updates as part of the SAP Business Network migration to BTP.
📌 Managed Gateway for Spend & Network: SAP's integration service sitting between your ERP (typically SAP S/4HANA or ECC) and SAP Business Network and the Ariba applications.
It handles the mapping, routing, and monitoring of documents so that each customer does not have to build and maintain point-to-point interfaces of their own between different SAP systems.
📌 Endpoints: the addresses systems use to reach each other (e.g. the URL each side sends its documents to).
When a platform moves, endpoints often change and both sides have to be repointed, which is exactly the manual work SAP is committing that Managed Gateway customers will not have to do here.
However, this is separate from the migration from BTP Neo to Cloud Foundry for Managed Gateway. If your organization has not yet completed that separate migration, your IT team should refer to this link for the latest guidance.
📌 BTP Neo: the older of SAP's two BTP environments, built on SAP's own proprietary technology. SAP is retiring it, so anything still running there has to move.
📌 Cloud Foundry: the open-source-based environment that is now the standard for BTP. Moving from Neo to Cloud Foundry changes the environment underneath a service, not what the service does.
If these terms are foreign to you and your IT teams, then most likely not applicable to you.
This visual highlights the CIG upgrade that customers manage themselves, along with the key things to look out for:
Here's the link to a set of tutorials (in English) for buyers experiencing SAP Business Network on BTP.
So What?
This migration is not one you can opt into or out of, and it will (unfortunately) not hand you new business capabilities on the day it lands. It is the toll you pay to stay on the road (although you’re transitioning to a newer road).
Here is what that means in practice.
If you are a procurement professional
Nothing in your process breaks, but your screenshots do. Work instructions, supplier training decks, and internal SOPs that show the old interface will be out of date the day your wave lands. Budget a few days of content refresh, not a change program.
The 30-day notice is your clock, and it needs an owner. Decide now who receives the migration notification and who is accountable for acting on it. These notices tend to land in a shared inbox and sit there.
Tell your suppliers before SAP does. Your strategic suppliers will migrate on their own schedule, not yours, and they will ask your category managers what changed. A short heads-up note protects your service desk.
Do not sell this internally as new functionality. SAP is explicit that features and functions are unchanged. Promising AI agents and advanced analytics on the back of this migration only sets your stakeholders up to be disappointed.
Check what is in flight. A large sourcing event, a wave of supplier onboarding, or a year-end invoice crunch sitting on top of your migration date is a legitimate reason to request a delay through SAP for Me. That channel exists; use it deliberately rather than reflexively.
If you are the IT business partner
Preserved is not the same as tested. Integrations, transaction rules, catalogs, and child accounts carry over automatically, but use the 30-day window to regression test your highest-volume flows: PO transmission, invoicing, catalog publication, and any custom transaction rules.
Plan time to monitor transactions after migration. Yes, this is a “key-in-hand” migration service provided by SAP. However, like any technological migration, things can break along the way for all sorts of reasons… Ensure you’re monitoring transactions after migration and flagging any issues to SAP promptly for resolution.
Managed Gateway has two separate stories, and they are easy to confuse. The BTP migration requires no manual endpoint updates. The move from BTP Neo to Cloud Foundry is a different, customer-owned migration. If your organization has not completed it, that work is yours and it does not wait for a wave assignment.
The more of the network you use, the later you migrate. SAP sequences the waves by complexity, so the organizations running the most Business Network functionality go last. Supply Chain Collaboration is the clearest example: those waves are expected to begin in the second half of 2026. If that is you, plan for a late slot rather than an early one, and do not assume a single wave carries your SCC activity on both the buyer and the supplier side.
You do not get to pick your wave, only to negotiate it. SAP assigns placement based on deployed features, configuration, and usage. A delay request needs your scheduled date, a business reason, and a proposed alternative that still falls within 2026.
If you are anxious to get the rest of your Ariba suite to next-gen…
This is the gate, not the prize. Business Network on BTP is a prerequisite. None of the next-gen functionality you are waiting for unlocks until you are through it, and the modules then follow on a separate timeline of their own.
The fastest route to next-gen is an uneventful network migration. Every delay you request pushes back the start of the module conversations. If your calendar can absorb the wave when SAP offers it, take it.
Treat 2026 as a foundation year in your roadmap and your budget. The value case for next-gen Ariba is real, but it lands in 2027 and beyond for most organizations. Fund the plumbing now and set that expectation with your CFO before someone else sets a different one.
You may be able to start using Joule / AI Agent functionality before migration. But, ensure you understand any migration impacts before you invest significant time and effort deploying these.
The bottom line: for most organizations this is a low-risk migration with a mandatory destination, no reward for arriving early, but a real cost to arriving unprepared. Assign an owner, watch for the notice, test what matters, and keep your suppliers informed. The interesting work starts on the other side of this migration.
Disclosure: This article represents the understanding and views of the author at the time of writing. /n Procurement is an independent publication and is not affiliated with, endorsed by, or sponsored by SAP. Readers should independently validate all information provided before making any major business decisions. Use at your own risk.
Worth Repeating…
Change is the law of life. And those who look only to the past or present are certain to miss the future.
👀 From the Archives…
Wrap Up
Get more from your SAP investment.
AI-powered intake and orchestration can help close the gap between what your ERP can do and what your process actually needs. This ebook, developed with Tonkean, looks at how to reduce manual work, streamline P2P flows, and create better coordination across your procurement tech stack.A source-to-pay rollout does not fail because the ambition is too high.
It fails when teams take on too much before the foundations are in place. This conversation explored a more practical path forward: choose the right starting point, create early wins, and build the momentum that makes broader transformation possible. In partnership with ConvergentIS.
— The /n Procurement Team