Business One to S/4HANA Is a Re-Implementation, Not an Upgrade#
SAP Business One and SAP S/4HANA are different products with different architectures. The migration is essentially a re-implementation of business processes in the more capable platform, not a version upgrade. Plan accordingly.
This article covers the honest playbook for ANZ businesses considering the migration.
Why Businesses Migrate Business One to S/4HANA#
Common drivers:
- Outgrowing SMB capability. Business One scales to ~100 users and modest transaction volumes; S/4HANA scales to enterprise.
- Multi-entity consolidation needs. Business One handles small multi-entity; S/4HANA handles complex global consolidation.
- Industry-specific compliance. Pharmaceuticals, aerospace, regulated process manufacturing may require S/4HANA's industry depth.
- Integration to broader SAP ecosystem. SAP S/4HANA integrates more deeply with SAP Ariba, SAP SuccessFactors, SAP Hybris, etc.
- Acquisition or strategic decision. Sometimes the migration is mandated by acquiring company or strategic platform decision.
When Migration Isn't Justified#
Business One is sometimes the right long-term home:
- Business genuinely operates at SMB scale with simple operations
- Customisation depth in Business One would be very expensive to rebuild
- Total revenue doesn't justify the implementation cost
- No multi-entity or international expansion plans
- IT capability is limited
For these businesses, Business One on subscription or perpetual licensing is sustainable for many years.
The Three S/4HANA Deployment Options#
Public Cloud (RISE with SAP). - SAP-managed multi-tenant cloud - Lower cost, faster deployment - Limited customisation (SAP's "Clean Core" approach) - Standard processes, minimal modifications - Best for businesses adopting SAP best practices
Private Cloud. - Dedicated infrastructure (typically Azure or AWS) - More customisation flexibility - Higher cost than Public Cloud - Customer-controlled patching and version management - Best for businesses needing customisation depth
On-Premise. - Maximum customisation and control - Highest cost - Requires significant IT capability - Customer-managed infrastructure - Becoming less common; SAP recommends cloud variants
For most ANZ Business One migrations, Public Cloud (RISE) or Private Cloud are the right choices. On-premise is selected only when specific customisation or data sovereignty requirements demand it.
Migration Cost Reality#
Business One → S/4HANA Public Cloud#
| Scope | Cost range |
|---|---|
| SMB to mid-market (50-100 users, single entity) | NZ$500,000–1,000,000 |
| Mid-market (100-200 users, multi-entity) | NZ$1,000,000–2,500,000 |
| Upper-mid-market (200+ users, complex operations) | NZ$2,500,000+ |
Business One → S/4HANA Private Cloud#
| Scope | Cost range |
|---|---|
| SMB to mid-market | NZ$800,000–1,800,000 |
| Mid-market with customisation | NZ$1,500,000–4,000,000 |
| Upper-mid-market with industry edition | NZ$3,000,000+ |
Costs include implementation, licences (first year), data migration, integration rebuild, training, and project management. Ongoing licences run NZ$200,000–800,000/year depending on user count and modules.
The Migration Playbook (Five Phases)#
Phase 1: Business Case and Discovery (8-16 weeks)#
Activities: - Document current Business One processes - Identify "Clean Core" candidates (processes to standardise vs customise) - Map customisations and decide retain/rebuild/eliminate - Build business case with ROI modelling - Select deployment option (Public/Private/On-prem) - Select implementation partner
Key insight: This phase often takes longer than businesses expect. The migration is strategic, not just technical.
Phase 2: Design and Configuration (16-32 weeks)#
Activities: - Implement S/4HANA standard processes (Activate methodology) - Configure modules for required business functions - Build custom extensions where retain decision was made - Configure multi-entity structure (if applicable) - Build integrations (typically rebuilt from Business One integrations) - Configure compliance and audit controls
Common mistake: Trying to recreate Business One exactly. S/4HANA is more capable; force-fitting Business One workflows wastes the migration.
Phase 3: Data Migration and Testing (12-24 weeks)#
Activities: - Build data migration scripts - Migrate test data (subset) - Validate financial reconciliation - User acceptance testing - Performance testing for scale validation - Iterate based on findings
S/4HANA-specific consideration: SAP HANA database performance characteristics differ from Business One's SQL Server. Performance testing validates that complex queries run in expected time.
Phase 4: Parallel Run (8-16 weeks)#
Activities: - Business One remains production - Mirror critical transactions in S/4HANA - Reconcile financials between systems - Train users (significant effort for S/4HANA transition) - Iterative cutover preparation
S/4HANA-specific: Parallel running for at least one full quarter is typical because the financial close processes differ significantly between Business One and S/4HANA.
Phase 5: Cutover and Hypercare (8-16 weeks)#
Activities: - Final data migration - Cutover to S/4HANA production - Business One becomes read-only - Hypercare period with intense support - Gradual transition from partner-managed to internal-managed
Customisation Strategy: Clean Core or Customise?#
SAP's "Clean Core" methodology recommends: - Use S/4HANA standard processes wherever possible - Customise via Side-by-Side Extensibility (SAP BTP) - Avoid customising the core S/4HANA codebase - Use SAP Build Apps for low-code custom interfaces
Why Clean Core matters: Customisations that modify the S/4HANA core make future upgrades expensive. Clean Core maintains upgrade simplicity.
For migrations from heavily-customised Business One, Clean Core requires re-architecting processes around SAP standard rather than replicating Business One customisations.
Data Migration Considerations#
What Migrates#
- Customer/vendor master records
- Item master records (with significant restructuring)
- Chart of accounts (typically redesigned)
- Open transactions (AR, AP, inventory)
- 2-3 years of historical transactions
What Doesn't Migrate Easily#
- Custom code from Business One
- Custom screens and workflows
- Reports designed for Business One's reporting tool
- Integration logic for Business One-specific APIs
These need to be rebuilt in S/4HANA-native approaches.
Integration Rebuild#
Business One integrations don't port. Each needs rebuild:
| Integration | S/4HANA approach |
|---|---|
| Banking | SAP Bank Communication Management |
| Payroll | SAP SuccessFactors or third-party (Australian STP, NZ payroll) |
| Ecommerce | SAP Commerce Cloud or SAP-certified connectors |
| CRM | SAP Sales Cloud or third-party (Salesforce, HubSpot) |
| Manufacturing | S/4HANA Manufacturing modules |
| BI/Reporting | SAP Analytics Cloud (SAC) replaces Business One reports |
Integration rebuild can be 20-40% of total migration cost.
Training and Change Management#
S/4HANA user experience differs significantly from Business One: - Different navigation patterns - Different process flows - New reporting and analytics - New mobile capabilities
Training investment is significant: typically NZ$10,000-50,000+ in formal training plus extensive on-the-job learning during hypercare.
Common Migration Failure Patterns#
- Underestimating customisation rebuild cost. Business One customisations don't port; rebuilding them in S/4HANA Clean Core is expensive.
- Insufficient parallel running. Cutover too quickly creates production issues that cost more than parallel-run weeks would have.
- Treating it as upgrade rather than re-implementation. S/4HANA is a different product, not Business One v2.
- Inadequate change management. S/4HANA UX differs significantly; users resist if not properly prepared.
- Wrong deployment option choice. Customisation-heavy migrations to Public Cloud (RISE) fail because of Clean Core constraints.
Alternative: Stay on Business One#
Before committing to S/4HANA migration, honestly evaluate:
- Is Business One actually constraining your business?
- Are there Business One-specific extensions that solve current pain points?
- Could SAP Business One Cloud handle scale concerns?
- Is the multi-million-dollar migration justified by the operational gain?
Many ANZ businesses stay on Business One indefinitely. The migration to S/4HANA is justified by scale, complexity, or strategic alignment — not by philosophy.
What to Ask Your Migration Partner#
- Show me 3 ANZ Business One → S/4HANA migrations with references.
- What's the partner's Clean Core methodology?
- How does the partner handle customisation decisions?
- What's the realistic timeline for my specific Business One configuration?
- What's the post-migration ongoing partner relationship look like?
See Also#
For broader context, see SAP Business One Guide, SAP S/4HANA Implementation Guide, SAP Implementation Complete Guide, Why ERP Implementations Fail, and Data Migration Disasters Case Studies.