Start with a defined next step
Request an ERP modernization workshop
Frame ERP boundaries, customizations, data, workflows, integration and retain/extend/replace decisions.
Page purpose
Know what you provide and what you receive when you request an erp modernization workshop.
Choose the ERP modernization workshop when stakeholders first need to align a defined ERP decision, its business boundaries, and the evidence a later assessment would require. It is a facilitated framing session—not the portfolio comparison of an enterprise systems assessment, the workload analysis of cloud readiness, or a complete ERP product selection or implementation estimate.
Initial inputs: high-level ERP products and versions, in-scope companies or functions, major customizations, known pain points, surrounding applications and interfaces, decision timing, and participant roles. Immediate output: fit, participant and preparation guidance, and a proposed workshop boundary. The workshop output is a shared decision brief, assumptions, option questions, unresolved evidence, and a recommended assessment or proof scope. Licensed software, credentials, personal or financial records, contracts, and production extracts do not belong in the public form.
When to use this step
When is this the appropriate next step?
- Stakeholders use different definitions of ERP scope and modernization success.
- Customizations and satellite tools are discussed without evidence of use or business value.
- Upgrade versus replacement becomes a binary argument before capability-level options are examined.
What you receive
What you receive after fit is reviewed.
- Initial output: workshop fit, participant, scope, and preparation brief.
- Facilitated maps of capabilities, system boundaries, pain points, and decisions.
- A decision brief with assumptions, option hypotheses, and open evidence questions.
- A recommended assessment or proof scope, not an unsupported implementation promise.
- A record of exclusions, dependencies, and authorized follow-up owners.
What happens next
What happens after the request is submitted.
- Confirm the ERP landscape, business scope, participants, and decision to frame.
- Map critical capabilities, customizations, interfaces, data, and workarounds.
- Separate verified constraints from preferences and product assumptions.
- Compare capability-level modernization options and transition implications.
- Agree the evidence and ownership needed for the next decision.
What to prepare
Information that makes the conversation useful.
- Which companies, functions, modules, and surrounding systems are in scope.
- Which capabilities require preservation, simplification, differentiation, or replacement.
- Which facts need a deeper assessment before options can be selected.
Information safety
Information that should not be sent through a public form.
- Submitting sensitive financial data, employee records, credentials, contracts, or licensed materials.
- Allowing product preference to substitute for capability and transition evidence.
- Treating a workshop output as a final architecture, estimate, or procurement decision.
Decision questions
Know the boundaries of the next step.
What decision does the ERP workshop produce?
It aligns the decision, boundaries, assumptions, option questions, and evidence required for the next step. Product selection is a separate decision requiring agreed requirements, candidate options, evaluation criteria, and procurement responsibilities beyond a framing workshop.
What information is safe for the initial request?
Share product families, approximate versions, company or function scope, major pain points, broad interface counts, and the decision deadline. Do not attach data exports, contracts, credentials, personal records, or confidential customization code.