SAP S/4HANA Greenfield Implementation Guide: Every Phase from Discover to Hypercare

SAP's 2027 deadline for mainstream ECC support is no longer a distant concern. For Canadian enterprises choosing a greenfield S/4HANA implementation, every configuration decision is deliberate: no legacy carry-forward, no inherited technical debt. This guide walks through every phase of SAP Activate for a greenfield deployment, with realistic timelines, budget benchmarks in Canadian dollars, and the Canadian-specific considerations that generic guides ignore.

SAP's own data indicates that roughly 60% of S/4HANA projects are greenfield implementations. The appeal is clear: a clean system built on SAP best practices, designed for Clean Core from day one. But "clean start" does not mean "simple." A mid-market greenfield implementation touches every business process, every master data record, and every integration point in your organisation.

What Is an SAP S/4HANA Greenfield Implementation and When Does It Make Sense?

A greenfield implementation starts from a blank S/4HANA system. You configure everything from scratch using SAP best practices as the baseline, then adjust for your specific business requirements. No legacy configuration, no historical data migration constraints, no inherited custom code.

Three implementation paths exist for moving to S/4HANA:

• Greenfield (new implementation) — Fresh system, fit-to-standard approach, Clean Core from day one. Best when ECC is heavily customized, the chart of accounts needs restructuring, or you are consolidating multiple ERP instances.
• Brownfield (system conversion) — Migrates existing ECC configuration, custom code, and historical data to S/4HANA. Faster but carries forward technical debt. Best when your current processes work well and customizations are manageable.
• Bluefield (selective data transition) — Combines elements of both. Selectively migrates data and configuration while restructuring other areas. Best for complex landscapes with partial modernization needs.

Greenfield is the right choice when your ECC system has accumulated hundreds of custom objects (Z-code), your organizational structure has changed significantly since the original implementation, or you want to take advantage of S/4HANA's architectural changes from the start. Those architectural changes are substantial:

• Business Partner replaces separate customer and vendor master records with a unified data model
• Universal Journal (ACDOCA) merges FI and CO postings into a single table, eliminating reconciliation
• MATDOC replaces MKPF/MSEG for inventory management with a simplified document model
• Fiori-based UI replaces SAP GUI as the primary user interface
• Clean Core principle moves custom extensions to SAP BTP instead of embedding them in the ERP core

For Canadian enterprises, greenfield has an additional advantage: bilingual (English/French) requirements, multi-provincial tax configuration, and Canadian banking formats are easier to implement correctly in a new system than to retrofit into a converted one.

How Does the SAP Activate Methodology Structure a Greenfield Project?

SAP Activate is SAP's implementation methodology for S/4HANA. It organizes the project into six phases:

Each phase has defined deliverables, quality gates, and accelerators (pre-built content from SAP Best Practices). The methodology is supported by SAP Cloud ALM for project management, testing, and monitoring. The following sections walk through each phase with the detail you need for planning.

Phase 1: Discover — Building the Business Case (Weeks 1–4)

The Discover phase answers two questions: why are we doing this, and what will it cost? This is where the digital transformation vision meets financial reality.

Key Activities

• SAP Readiness Check and Transformation Navigator to assess your current ECC landscape
• High-level scope definition: which modules, which business processes, which entities
• Deployment decision: S/4HANA Cloud Public Edition, Cloud Private Edition, or on-premise
• RISE with SAP evaluation (bundled infrastructure, licensing, and tools)
• Custom code analysis: how many Z-objects exist, how many are actively used, how many can be retired
• Budget estimation and high-level roadmap

Canadian angle: The technical uncertainty involved in custom integration development during a greenfield implementation may qualify for SR&ED (Scientific Research and Experimental Development) tax credits. This is worth validating with a tax advisor during the business case phase, as eligible expenditures can offset 15-35% of qualifying costs depending on the province.

Budget benchmark: The Discovery phase typically runs $50,000 to $150,000 CAD with an external partner, depending on landscape complexity.

Phase 2: Prepare — Project Foundation (Weeks 4–10)

Prepare establishes the governance structure, provisions the system landscape, and defines the organizational structures that everything else builds on. Decisions made here are expensive to change later.

Project Governance

• Project charter with executive sponsorship
• Steering committee with monthly cadence
• RACI matrix for every workstream: functional, technical, data migration, integration, change management
• Implementation partner selection (Big 4, mid-tier, or boutique SAP firms)

System Landscape

• DEV / QAS / PRD system provisioning
• SAP Best Practice content activation (pre-configured processes for each module)
• Fiori Launchpad setup and initial role design
• SAP Cloud ALM or Solution Manager for project management and testing

Organizational Structures

These are the backbone of every SAP process. Get them wrong and everything built on top is compromised:

• Client and company codes
• Controlling areas and cost centre hierarchies
• Plants, storage locations, and shipping points
• Sales organizations, distribution channels, and divisions
• Purchasing organizations

Canadian considerations: Multi-currency configuration (CAD/USD at minimum for firms with US operations), bilingual output forms and Fiori apps, GST/HST/PST/QST tax procedure configuration by province, and CRA reporting requirements should all be scoped during Prepare, not discovered during Realize.

AI readiness decision point: If you plan to activate SAP Joule or SAP Business AI features post go-live, the data architecture decisions you make in Prepare directly affect AI readiness. Clean master data and consistent coding are prerequisites. For a detailed walkthrough, see our guide to adding generative AI to S/4HANA.

Budget benchmark: $100,000 to $300,000 CAD for partner effort in Prepare.

Phase 3: Explore — Fit-to-Standard Workshops (Weeks 8–18)

Explore is where the real work begins. Functional consultants run fit-to-standard workshops with your business process owners, walking through SAP best practice processes and identifying where your requirements differ from the standard.

Module-by-Module Workshop Coverage

Gap Analysis and Resolution

Every gap identified in workshops falls into one of four categories:

1. Adopt standard — Change the business process to match SAP best practice. This is the preferred option for Clean Core.
2. Configure — Use existing SAP configuration options (SPRO) to match the requirement without custom code.
3. Extend via BTP — Build the solution as a side-by-side extension on SAP Business Technology Platform. For more on this approach, see our guide to SAP BTP for Canadian enterprises.
4. Build custom (last resort) — Custom ABAP development in the S/4HANA core. Every custom object adds upgrade risk and maintenance cost.

Integration Architecture

Explore is also where you map every integration point. Common cross-module and external integrations include:

• MM-FI — Automatic accounting entries from procurement transactions
• SD-FI — Revenue recognition and billing integration
• PP-MM — Material consumption and goods movements from production
• EWM-MM — Warehouse management integration for inventory accuracy
• External systems — EDI with trading partners, CPI/API integrations, bank connectivity, CRA filing

Canadian angle: PIPEDA applies to any module handling personal data. Quebec's Law 25 and British Columbia and Alberta's PIPA legislation may impose additional requirements beyond PIPEDA for employee and customer data. Factor these into your data classification during Explore. For reporting design considerations, see how natural language queries can replace complex SAP report building.

Phase 4: Realize — Configure, Build, and Migrate (Weeks 16–40)

Realize is the longest and most resource-intensive phase, typically consuming 40-50% of the total implementation budget. This is where fit-to-standard decisions become working system configuration.

Configuration Sprints

Realize uses agile delivery in 2-3 week sprints, each ending with a demo to business stakeholders. Key configuration areas in SPRO include:

• Enterprise structure assignments
• Document types and number ranges
• Pricing procedures and condition records
• Movement types for inventory management
• Output control using BRF+ (replacing legacy NACE)
• Account determination (OBYC for MM, VKOA for SD)
• Workflow configuration for approvals
• User roles and authorization objects
• Forms management (Adobe Forms or output via BTP)

Data Migration Strategy

Data migration is consistently the most underestimated workstream in SAP implementations. Plan for 25-30% of total project effort. The common mistake is trying to cleanse data during migration instead of before it.

Migration objects for a typical greenfield include:

• Master data — Business Partners (customers, vendors), materials, BOMs, routings, GL accounts, cost centres
• Open transactions — Open purchase orders, open sales orders, open deliveries
• Balances — GL balances, subledger balances, bank balances
• Serial numbers and batches — For industries requiring lot traceability

SAP Migration Cockpit is the standard tool. Plan for 3-4 full trial migration loads before cutover. Each trial load validates data quality, mapping rules, and load performance.

Canadian angle: Many Canadian firms operate separate legal entities for US operations. Multi-entity migrations add significant complexity around intercompany configuration, transfer pricing, and multi-currency GL balances. Canadian banking formats (CPA-005 for EFT) must be tested during migration trials, not discovered at cutover.

Integration Development

Middleware selection drives integration architecture. Options include SAP Integration Suite on BTP, third-party platforms (MuleSoft, Boomi, Dell Boomi), or direct API development. For Canadian enterprises evaluating BTP as the integration platform, see our detailed guide on SAP BTP for digital transformation.

Common integration points for Canadian firms include banks (CPA-005 format for EFT payments), CRA for GST/HST filing, EDI with trading partners (especially retail and automotive supply chains), warehouse management systems, and manufacturing execution systems.

Testing Strategy

Testing in Realize follows a progressive sequence:

1. Unit testing — Individual configuration items tested per sprint by the functional team
2. Integration testing — End-to-end business process testing across modules (e.g., a complete procure-to-pay cycle from requisition through payment)
3. User acceptance testing (UAT) — Business users validate that the system supports their daily work. Do not compress this phase to meet go-live dates.
4. Performance and stress testing — Validate response times under expected production volumes
5. Regression testing — Verify that transports to QAS do not break previously tested functionality

Budget benchmark: Realize typically runs $600,000 to $4,000,000 CAD for mid-market implementations, depending on module count and integration complexity.

Phase 5: Deploy — Cutover and Go-Live (Weeks 38–48)

Deploy is the highest-stakes phase. A well-planned cutover weekend feels anticlimactic because every step has been rehearsed. A poorly planned one becomes a company-wide crisis.

Cutover Planning

• Cutover runbook — Minute-by-minute schedule for every activity during the cutover window. Who does what, in what sequence, with what dependencies.
• Dress rehearsals — At least 2, ideally 3 full cutover rehearsals. Each rehearsal validates timing, identifies bottlenecks, and trains the team on the sequence.
• Go/no-go criteria — Pre-defined checklist: data migration success rate, critical defect count, business sign-off status, role provisioning, batch job scheduling.
• Communication plan — Internal stakeholders, customers (especially if portals or EDI change), suppliers, banks, and external auditors.

Go-Live Weekend Activities

• Final data migration (delta loads for transactional data created since the last full load)
• Legacy system freeze
• Open balance uploads and reconciliation
• Integration cutover: switch interfaces from legacy to S/4HANA endpoints
• Role activation and user access provisioning
• Transport to PRD and smoke testing of critical business processes
• Batch job activation and background monitoring
• Business sign-off before opening to all users

Change Management

End-user training should be role-based and focused on Fiori, not generic SAP GUI training. The move from SAP GUI to Fiori is the most visible change and generates the most resistance. Plan for a key user (super-user) network of 1 key user per 20-30 end users to provide first-line support after go-live.

Canadian angle: If going live near fiscal year-end or quarter-end, coordinate with external auditors. CRA GST/HST filing deadlines do not move for your go-live. Plan to run parallel returns in the old and new system for at least one filing period.

Budget benchmark: Deploy phase including training: $150,000 to $500,000 CAD.

Phase 6: Run — Hypercare and Continuous Improvement (Weeks 48+)

Go-live is not the finish line. The Run phase begins with intensive hypercare support and transitions into continuous improvement.

Hypercare (4–8 Weeks)

• War room structure with functional leads and technical team on standby
• Issue triage: P1 (business-stopping), P2 (workaround available), P3 (enhancement)
• Daily standups with business process owners during the first 2 weeks, transitioning to weekly
• Critical defect resolution with same-day transport to production
• Performance monitoring and tuning

Stabilization metrics to track: Transaction processing time, error rates by module, help desk ticket volume (should trend downward weekly), and month-end close duration compared to legacy system.

Continuous Improvement and AI Activation

Once the system stabilizes, the clean data foundation you built during implementation becomes the platform for AI and automation:

• Fiori adoption — Expand Fiori apps beyond the initial go-live set based on user feedback and usage analytics
• Embedded analytics — Activate S/4HANA's built-in analytical capabilities without a separate BW system
• SAP Business AI — Intelligent invoice matching, automated GL account recommendation, predictive delivery scheduling
• SAP Joule — Generative AI copilot for conversational interaction with SAP data and processes
• Process automation — SAP Build Process Automation for repetitive tasks like journal entry posting and report distribution
• KPI dashboards — Real-time operational and financial dashboards using SAP Analytics Cloud

For specific AI use cases that build on a clean S/4HANA foundation, see our guides to predictive maintenance in SAP PM and AI-powered production scheduling.

What Are the Most Common Greenfield Implementation Pitfalls?

• Underestimating data migration — Consistently the number one cause of timeline slippage. Data migration takes 25-30% of total project effort. Budget accordingly and start data cleansing in the Prepare phase, not Realize.
• Skipping fit-to-standard — Jumping to custom development instead of challenging business processes to adopt SAP standard. Every custom object you avoid building is maintenance and upgrade risk you avoid permanently.
• Insufficient change management budget — Prosci research shows projects with excellent change management are 6x more likely to meet objectives. Budget 10-15% of total project cost for training, communication, and resistance management.
• Compressing UAT — Cutting user acceptance testing to meet go-live dates moves defects from pre-production to production, where they cost 10x more to fix and directly impact business operations.
• Ignoring Clean Core — Building custom code in the ERP core instead of extending via BTP creates the same upgrade lock-in you are trying to escape from ECC.
• Not planning for AI — Implementing S/4HANA in 2026 without considering AI readiness is like building a house without network cabling in 2005. The foundation decisions you make now determine what is possible later.

What Does an SAP S/4HANA Greenfield Implementation Cost in Canada?

Realistic budget ranges by company size, in Canadian dollars:

Typical budget breakdown: ~35% consulting and labour, ~25% software licences, ~15% infrastructure, ~15% data migration and integration development, ~10% change management and training.

Canadian-specific cost factors: Bilingual requirements add 5-10% to forms, training materials, and documentation. Multi-provincial tax configuration is a non-trivial effort for firms operating across provinces. Canadian implementation partner rates typically run $200-$350/hour CAD for senior consultants and $150-$250/hour for functional analysts.

How Can AI Accelerate Your S/4HANA Implementation and Post-Go-Live Operations?

AI is relevant at two stages: during the implementation itself, and as a capability you activate after go-live.

During implementation: AI tools can accelerate test script generation, validate data mapping rules, review custom ABAP and Fiori code for quality issues, and generate training materials. These are supplementary tools that reduce effort, not replacements for experienced consultants.

Post go-live: A clean S/4HANA foundation unlocks SAP Business AI features that require consistent master data, unified journal entries, and a Clean Core architecture:

• Intelligent invoice matching that auto-resolves PO/GR/invoice discrepancies
• Automated GL account recommendation for manual journal entries
• Predictive delivery scheduling based on historical fulfilment patterns
• Natural language reporting via SAP Joule
• Demand forecasting using machine learning on AI Core

Organisations implementing S/4HANA greenfield in 2026 should design for AI from the start, not bolt it on later. For a deeper look, see our guide to adding generative AI to your SAP S/4HANA environment and our analysis of Oracle and SAP AI roadmaps for 2026.

Key Takeaways