We’re not here to sell you a project. We’re here to help you understand what you’re looking at – so you can make a confident, informed decision at your own pace.
The number and type of on-premise source systems are among the key drivers of migration effort. Each system requires its own data extraction and connection setup.
Identifying cloud sources defines the integration architecture and connectivity methods. This helps us estimate scope and cost and determine if security components, like SAP Cloud Connector, are needed.
Your current reporting tools determine what needs to be migrated, re-pointed, or replaced. BOBJ, in particular, has a specific migration path to BDC that we need to account for.
Planning tools built on BPC often have deep BW integrations – models, input forms, workflows – and migrating them is typically a separate workstream that requires a separate estimate.
The level of customization is one of the strongest predictors of migration cost. The more custom logic exists, the more analysis, re-engineering, and testing are required to move safely to BDC.
Knowing your target on-premise connections helps us estimate the number of Data Provisioning Agents required and size the connectivity layer in BDC.
The number and type of cloud connections directly determine how many Cloud Connectors will be needed and how the integration layer in BDC should be designed.
Knowing your target reporting tool helps us design the best possible integration setup within BDC. For example, SAC has deep native integration with BDC. Other tools might require a different integration approach.
Planning requires separate setup, user licensing, and model design in BDC. Knowing this upfront lets us include the right workstreams in the estimate.
Each business domain typically has its own data flows and reports. The number and complexity of domains are key factors in scoping the migration.
With more than one system (PROD + DEV + QA), the migration scope increases, and the migration team will have to handle added complexity and dependencies.
Data volume affects migration duration, potential downtime windows, infrastructure sizing, and the complexity of initial data loads in BDC.
User numbers inform performance requirements, system sizing, and the effort needed for user training and change management during the transition.
Planning users have different requirements than reporting users – they need write-back access, input forms, and workflow support. This affects both the design and testing scope.
The approach is one of the biggest variables in total project cost and timeline. A Lift & Shift is faster but may carry over complexity; a greenfield is thorough but takes longer.
Knowing your primary concern helps us give you a more useful first response – we can address it directly rather than giving you a generic overview.
Thanks for your answers! We’ll review them and get back to you within 24 hours with a clear, easy-to-understand estimate.
It’s completely free and comes with no obligations.
