How SAP projects are structured
SAP projects come in recurring shapes — greenfield builds, brownfield conversions, template rollouts, upgrades and clean-ups, and AMS — and the shape decides what the work feels like from inside. Every SAP job ad and staffing call assumes you already know which is which.
Greenfield: the new build
A fresh implementation — new system, processes designed from scratch (or from a standard template). Maximum design work, maximum workshops, the full lifecycle from blueprint to go-live. Best learning environment in the ecosystem; also the longest programmes. Every role appears here, from functional consultants to architects.
Brownfield: the conversion
An existing system converted in place to the newer platform, history and customisations included. Less process redesign, more analysis: what breaks, which custom code survives, what must be remediated. Technical tracks — developers, Basis — carry unusual weight in these.
Rollouts: the template repeated
A corporate template deployed country by country or plant by plant. The design questions are mostly settled; the work is localisation — legal requirements, local processes, data migration, training. Shorter cycles, more travel variety, and a classic environment for juniors to compound experience fast: same problems, new context, every few months.
Upgrades and clean-ups
Focused technical programmes: version upgrades, moving custom developments to clean-core patterns, consolidating landscapes, master-data harmonisation. Bounded scope, measurable outcomes — popular with specialists and freelancers.
AMS: the steady state
Everything above ends; the system keeps running for decades. Incident resolution, small enhancements, monitoring, period-end support — the continuous form of SAP work and the ecosystem's most reliable entry door.
Who is on an SAP project team?
Whatever the shape, the team is organised the same way: by stream. Each SAP area — finance, procurement, sales, manufacturing — gets a functional stream with a lead and one or more consultants, usually mirrored by a business process owner and key users on the client side. Around the streams sit the cross-cutting teams: developers and an integration team for everything configuration cannot do, Basis for the systems and transports, a data-migration team, a test manager who runs the integration test waves, and a change and training team. Above it all sit a project manager, a solution architect who owns the design across streams, and a steering committee that takes the decisions nobody else can. A greenfield build staffs every seat; a rollout reuses the template team with local functional support; AMS collapses the whole structure into a support organisation with the same areas as queues.
Which project shapes belong on your record?
More than one, over a career: the shapes are read as separate credentials, and each teaches something the others cannot.
- Hiring is shape-specific: "greenfield design experience" and "rollout experience" are different credentials — collect deliberately (how experience is read).
- Learning speed differs: greenfield teaches design, rollouts teach repetition-to-mastery, AMS teaches production truth.
- A balanced record — at least one big build plus live-system time — reads strongest over a career.
Related reading
- A day in the life of an SAP consultant
Four real days, one from each project phase — design, build, test, go-live.
- Understanding the SAP ecosystem
SAP, integrators, boutiques, in-house, AMS and freelance — the employer map.
- SAP Activate methodology explained
Discover to Run: the phases, fit-to-standard workshops, best-practice content, the break from ASAP, and what each phase means for your week.
- What the S/4HANA era means for your SAP career
What carries over, what's newly valuable, what fades — and how to position.
Work with SAP?
Join to get your public SAP profile. Your city appears on the map once 5 professionals are mapped there.