SAP PO to SAP Integration Suite · Timeline calculator
How long will your SAP PO migration take?
Enter your number of ICOs and get an indicative timeline, with and without the Rojo migration approach. It takes about a minute.
1
Your SAP PO landscape
Your SAP PO team, or the SAP Migration Assessment, can give you the ICO count.
Example: 500 ICOs. Drag the slider or type your own number.
Number of ICOsiICOs (Integrated Configuration objects) are the integration scenarios configured in your SAP PO system. A rough number is fine: the plan shows a range. We plan on a standard 1 ICO = 2 interfaces. The estimator covers up to 3,000 ICOs.
53,000
I already know my interface count (optional)Number of interfaces
Count distinct interfaces (sender, receiver and mapping combinations), not message-mapping rows. If you fill this in, it replaces the 2-per-ICO conversion.
Include a platform review and governance phaseiNaming, guidelines and set-up of SAP Integration Suite before migration starts. Adds 1 month to the plan.
✓
Your plan includes a 2-month pre-project and pilot
It shows how the whole migration will run before the main work starts.
2
See your full planYour migration timeline
Get your full migration plan
Leave your details to unlock the full plan on this page, download it as a PDF and receive a copy by email.
- The phases of your plan, month by month
- The comparison with and without the Rojo migration approach
- The assumptions behind the plan and suggested next steps
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Your full plan is unlocked below. A copy is on its way to your inbox.
Download as PDF- This is an indicative planning estimate, not an offer. A firm plan needs your SAP Migration Assessment and a scoping conversation.
- ICOs are converted at a standard 1 ICO = 2 interfaces; your actual ratio may differ, which is why the result is a range (±10% on the interface count). Duration depends on interface count, partner and business testing availability and decisions on scope (for example, interfaces with no traffic).
- Landscapes of fewer than 50 interfaces are planned as one compact 3-month delivery with no separate pre-project or platform review. Every larger plan includes a pre-project and pilot (2 months, or 1 month for landscapes of 150 ICOs or fewer). It shows how the migration will run (validated scope, tuned automation templates, B2B strategy, roadmap and risk register) before the main work starts.
- The comparison without the Rojo migration approach is a Rojo estimate: the migration itself takes about twice as long with the same team size.
- No prices, rates or team sizes are shown or used on this page.