SAP implementation discussions often start with familiar labels: Greenfield, Brownfield, Rollout, Conversion, Migration, and so on. These words are useful shortcuts, but they are not decisions by themselves.
A Greenfield project may still carry old process habits. A Brownfield project may still require major cleanup. A Rollout can be efficient only when the template is mature enough and local differences are not underestimated. A Conversion is technical in form, but it still depends on process, data, custom code, and integration readiness.
A better way to use the terms
- Use the label to describe the starting point, not to hide the work that remains.
- Separate process redesign, technical conversion, data migration, and organizational change.
- Make local exceptions visible early, especially in finance, procurement, sales, production, and logistics.
The implementation strategy should be a risk map. If it only becomes a project slogan, it will not help the team make better decisions.