SAP Implementation in ANZ: What Vendors Won't Tell You#
If you're considering SAP for your New Zealand or Australian organisation, you're facing a decision that will define your technology landscape for the next 10-15 years. SAP implementations are among the most complex enterprise technology projects—succeed, and you gain a platform that can scale globally; fail, and you'll spend years recovering.
The uncomfortable reality: SAP implementation success rates haven't meaningfully improved in two decades. The same patterns repeat: underestimated timelines, scope creep, partner dependencies, and the perpetual gap between what was sold and what gets delivered.
This guide provides an honest assessment of SAP implementation specifically for the ANZ market—covering S/4HANA deployment options, partner selection, timeline planning, and the unique challenges of implementing SAP at the edge of the world.
---
SAP S/4HANA: Your Deployment Options#
S/4HANA Cloud (Public Edition)#
Multi-tenant cloud with quarterly updates.
What it means: - You cannot stay on older versions—everyone upgrades together - Customisation is limited to configuration and approved extensions - Lower initial cost, but subscription commitment is long-term - Vendor manages infrastructure, but you manage process change
ANZ reality: - Data residency: Australian data centres available; verify NZ options - Partner ecosystem: Strong in Australia, limited in New Zealand - Best fit: Organisations willing to adopt standard SAP processes
Typical timeline: 12-18 months for mid-market, 18-30 months for enterprise.
Typical cost: $200-400/user/month subscription + $2-5M implementation.
S/4HANA Cloud (Private Edition)#
Single-tenant cloud with more flexibility.
What it means: - Your own instance with more customisation freedom - More control over upgrade timing - Higher cost than public cloud - Still vendor-managed infrastructure
ANZ reality: - Higher cost may be justified for complex manufacturing - Partner capability more critical due to customisation complexity - Better for organisations with unique processes
Typical timeline: 18-30 months.
Typical cost: $250-500/user/month + $3-8M implementation.
S/4HANA On-Premise#
Traditional perpetual license with annual support.
What it means: - Maximum control and customisation - You manage infrastructure, upgrades, security - Large upfront license cost - 18-22% annual support fees
ANZ reality: - Requires significant internal IT capability - Data sovereignty easier to guarantee - Being phased out strategically—vendor pushes cloud
Typical timeline: 18-36 months.
Typical cost: $3-8K/user license + $3-10M implementation + ongoing support.
---
The ANZ Partner Ecosystem Challenge#
Australia: Strong but Concentrated#
Major partners: - Deloitte, Accenture, Capgemini for enterprise - Boutique SAP specialists for mid-market - Strong implementation capability
Challenges: - High demand creates resource constraints - Premium pricing during peak periods - Quality varies significantly between engagement teams
New Zealand: Limited and Stretched#
Reality check: - Very few partners with local presence - Most implementations served from Australia - Limited deep SAP expertise resident in NZ - Partner resources stretched thin across multiple projects
What this means for your project: - Budget 20-30% more for partner travel and availability premiums - Verify actual team members—don't accept "we have NZ experience" - Consider Australian partners with genuine NZ references - Build internal capability from day one
---
Timeline Planning: What Actually Happens#
The Optimistic Vendor Timeline#
| Phase | Vendor Claims |
|---|---|
| Preparation | 2-3 months |
| Realisation | 4-6 months |
| Final Preparation | 2-3 months |
| Go-Live Support | 1-2 months |
| Total | 9-14 months |
The Realistic ANZ Timeline#
| Phase | Realistic Expectation |
|---|---|
| Vendor selection & contract | 2-4 months |
| Detailed planning | 2-3 months |
| Realisation (configuration, development) | 6-12 months |
| Testing (including remediation) | 3-4 months |
| Training & cutover | 2-3 months |
| Go-live & stabilisation | 2-3 months |
| Total | 17-29 months |
Why Timelines Slip#
Data migration: Always takes longer than estimated. Legacy data quality in ANZ organisations often worse than assumed.
Integration complexity: ANZ-specific integrations (banking, government, marketplaces) add unexpected complexity.
Resource availability: Partner resources may be stretched across multiple ANZ projects.
Decision velocity: Distributed decision-making across time zones can slow progress.
---
Cost Planning: The Real Numbers#
Implementation Costs (ANZ-Specific)#
| Component | Typical Range |
|---|---|
| Partner implementation services | $1.5-4M |
| Internal staff time (opportunity cost) | $500K-1.5M |
| Data migration | $300-800K |
| Integration development | $200-600K |
| Training development & delivery | $150-400K |
| Infrastructure (cloud or on-prem) | $100-500K |
| Contingency (15-25%) | $400K-1.5M |
| Total implementation | $3-9M |
Ongoing Costs (Annual)#
| Component | Typical Range |
|---|---|
| Subscription or support fees | $200-600K |
| Internal SAP team (2-4 FTE) | $300-600K |
| Partner managed services | $100-300K |
| Enhancement & optimisation | $100-200K |
| Total annual | $700K-1.7M |
Five-Year TCO#
Mid-market (100-200 users): $6-12M
Enterprise (500+ users): $15-35M
---
Critical Success Factors for ANZ Implementations#
1. Executive Sponsorship#
SAP implementations require sustained C-level commitment—not just signing cheques, but active involvement in key decisions.
What this means: - CEO or COO as executive sponsor (not just CIO) - Monthly steering committee with senior stakeholders - Executive willingness to make difficult trade-off decisions - Visible commitment to change, not just technology
2. Partner Selection Rigor#
The partner matters more than the software.
Due diligence checklist: - At least 3 references from similar-sized ANZ organisations - Specific team members named and verified (not just "we have experts") - Track record of completing projects, not just starting them - Financial stability check - Clear escalation paths to partner leadership
Red flags: - Vague team descriptions - References from different industries or sizes - Unwillingness to commit to fixed-price elements - Poor response time during sales
3. Process Standardisation Commitment#
SAP works best when you adapt to SAP, not when SAP adapts to you.
The question: Are you prepared to change your processes to fit SAP standard functionality?
If no: Budget 2-3x for customisation, accept longer timeline, higher risk.
If yes: Faster implementation, lower cost, easier upgrades.
4. Data Preparation Early#
Start data cleansing 6-12 months before implementation starts.
Common issues: - Incomplete master data - Inconsistent coding structures - Historical transactions that don't map cleanly - Missing documentation of current data structures
5. Internal Capability Building#
Don't outsource everything.
Build internal capability: - SAP-knowledgeable business analysts - Technical team for basic configuration - Power users who can train others - Future system ownership clarity
---
The ANZ-Specific Challenges#
Geographic Distance#
Challenge: SAP expertise concentrated in Europe and US, limited in ANZ.
Mitigation: - Build stronger internal capability - Budget for bringing in international expertise when needed - Consider near-shore development partners for technical work
Market Size#
Challenge: Small market means fewer local references, limited partner choice.
Mitigation: - Accept that you may be pioneer for your specific scenario - Join SAP user groups for peer learning - Budget for extra due diligence
Regulatory Environment#
Challenge: NZ/AU privacy, tax, and reporting requirements differ from global standards.
Mitigation: - Verify SAP capabilities for specific requirements - Budget for localisation work - Test reporting requirements early
Banking Integration#
Challenge: NZ/AU banking systems require specific integration formats.
Mitigation: - Verify SAP support for direct credit files, bank statement formats - Test bank integration early in project - Consider middleware for complex requirements
---
Monday Morning Action Plan#
This week:
- Assess Your Size and Complexity: Under 100 users? Consider Business One. Complex manufacturing? Plan for S/4HANA private or on-premise. Services organisation? Explore SAP's professional services capabilities.
- Build Your Business Case: Include 5-year TCO, not just implementation cost. Factor in ANZ premiums (partner travel, limited local expertise, currency exposure).
- Start Partner Due Diligence: List potential partners. Request references from similar ANZ organisations. Verify team members before signing.
- Assess Your Process Flexibility: How willing are you to change processes? Document non-negotiables vs. areas for compromise.
- Begin Data Assessment: Inventory your master data. Assess quality. Estimate cleansing effort.
---
Conclusion: SAP Is a Multi-Year Commitment#
SAP implementation is not a technology project—it's an organisational transformation. For ANZ organisations, the added complexity of limited local expertise, geographic distance from SAP ecosystem, and specific regulatory requirements means extra diligence is essential.
Success requires: - Realistic timeline and budget expectations - Rigorous partner selection - Commitment to process standardisation - Investment in internal capability - Executive sponsorship that goes beyond signing cheques
The organisations that succeed with SAP are those that enter with eyes open, budgets realistic, and leadership committed for the long haul.