When will your B2B migration actually be done?
Nine quick questions about your SAP PI/PO B2B landscape. We'll plot your go-live on a real calendar, weekends and public holidays included, then show you how much sooner you get there with Figaf.
·
Your go-live date
Worked out day by day, skipping weekends and public holidays.
A time plan comparison
Your classic plan next to the Figaf route, on one timeline.
A cost comparison
What each route costs at your developer rate, Figaf costs included.
Tweak the numbers
Everything updates as you type. Effort is in days per agreement; 1 day = 8 hours.
More than a faster migration
Functional
- One overview of your B2B landscape: partners, agreements, MIGs and MAGs in one place.
- Regression tests with real messages that you reuse for every future change, not just the migration.
- Groovy and XSLT editing, Git versioning and documentation built in.
- Monitoring and data-review tools for running B2B day to day.
Organizational
- The tool you migrate with is the tool you operate with. No hand-over gap after go-live.
- Partner onboarding becomes a repeatable process instead of a project every time.
- Consistent naming and structure across agreements, so anyone on the team can pick up any partner.
- Developers spend their time on new business, not on keeping the lights on.
Governance
- Change management with tickets linked to every change.
- Controlled transports through DEV, QA and PROD.
- Object tracking: see who changed what, when and why.
- A lower total cost of ownership: fewer incidents, faster fixes and a shorter time-to-market for new partners.
Time plan: classic vs Figaf
| Measure | Classic | With Figaf | Difference |
|---|
Cost: classic vs Figaf*
| At your rate | Classic | With Figaf | Difference |
|---|
* Prices are guidance only, see the disclaimer. For real numbers, contact Figaf.
Where the time goes
Days per agreement (1 day = 8 hours): your estimates for the classic route, next to the estimated effort with Figaf.
Fun facts for the steering committee
Your inputs
* Disclaimer: this calculator is for guidance only and does not constitute an offer. The figures are illustrative estimates. Figaf cannot guarantee that a migration can be delivered within them, with or without Figaf: actual effort, timelines and costs depend on your landscape, team and project conditions. The timeline uses 8-hour working days and your team's share of the work week. Public holidays are national (or for the region shown) and don't include company shutdowns or vacation; festival dates that follow lunar calendars (India, Singapore) are approximate and included up to 2030. Figaf prices are based on Figaf’s public list prices and may change: a one-time migration price per agreement, graduated as on the pricing page, a yearly DevOps + B2B license sized by managed objects, and an onboarding package with a two-day workshop and consulting along the way. Actual license costs depend on your project’s scope and terms. Contact Figaf for a binding quote.
Want these numbers for your real landscape?
30 minutes with a Figaf expert, walking through your B2B scenarios and how to make the case internally.