Every implementation project starts with the same optimism. The decision has been made. The licence is signed. Someone on the team has watched a demo and circled a go-live date on the calendar. What happens between that moment and the morning you actually open SAP Business One Cloud for the first time is the part that nobody explains in enough detail. This is that explanation.  The eight-week timeline below reflects how Ingold Solutions runs a standard SAP Business One Cloud implementation for a small or mid-sized business. Not a consultancy ideal — the practical reality of what disciplined scope management, careful data preparation, and experienced configuration look like, week by week.  Not every project fits this shape. Simpler deployments with clean data and a narrow scope can reach go-live in four to six weeks. More complex projects — multiple warehouses, manufacturing modules, external system integrations, significant data migration — typically run ten to sixteen weeks. But eight weeks, managed properly, is realistic for most SMBs implementing SAP Business One Cloud for the first time. 

	Phase	What Happens
Week 1	Discovery Workshop	Scope, process mapping, project plan, user and licence list
Week 2	Process Analysis	Configuration blueprint, chart of accounts, authorisation concept, document templates
Week 3	System Setup	Live company database built, all modules configured, compliance setup (ELSTER, DATEV)
Week 4	Data Migration	Master data, price lists, and opening balances imported and validated
Week 5	User Training	Role-based hands-on training in test environment with real migrated data
Week 6	Testing	End-to-end process testing, integration testing, user acceptance sign-off
Week 7	Go-Live Preparation	Cutover date locked, final data migration, user access activated, go-live checklist completed
Week 8	Launch	Live transactions processed, hyper-care support active, old system in read-only mode

  Source: Ingold Solutions implementation methodology, based on SAP's Accelerated Implementation Program (AIP). Package prices per Ingold Solutions published rates, April 2026. 

Week 1: Discovery Workshop 

The first week of a SAP Business One Cloud implementation is not spent configuring software. It is spent listening.  A good discovery workshop does one thing that saves significant time later: it establishes the gap between what a business thinks it needs and what it actually needs. Those two things are often different. A business owner who says 'we need inventory management' may mean batch tracking, serial number control, multi-warehouse bin transfers, and three separate purchase approval levels — or may mean a basic stock count and a reorder point. Finding out which in Week 1 costs nothing. Finding out in Week 6 costs a delay.  What Ingold Solutions covers in Week 1: 

• Current process documentation: how orders, purchases, and financial transactions flow today — not the idealised version, but what actually happens 

• System landscape review: what software is currently running, what data lives in it, and what format that data is in 

• Go-live date and governance: who owns decisions on the client side, who has sign-off authority, and who will be available each week 

• Scope definition: which modules are in scope for go-live and which are deferred to a Phase 2 

• User list and licence confirmation: who needs Professional access, who needs Limited, and which variant of Limited applies to each role 

The output is a signed project scope document and a project plan with weekly milestones. Nothing moves to Week 2 until both are agreed. This is not bureaucracy — it is the single most cost-effective step in any implementation. 

Week 2: Process Analysis 

With scope agreed, Week 2 goes deeper into the business processes that SAP Business One Cloud will actually run.  This is where the configuration consultant maps current business reality to SAP's process architecture. SAP Business One has a specific way of handling the procure-to-pay cycle, the order-to-cash cycle, and financial period-end — and every business has its own way of doing the same things. The mapping exercise identifies where SAP's standard configuration is an exact match, where it needs adjustment, and where a specific requirement will need a custom layout, user-defined field, or approval workflow.  In Week 2, Ingold Solutions will also: 

• Chart of accounts structure: SKR03 or SKR04 for German businesses, or a custom chart for specific segmentation requirements. This decision affects every financial posting in the system — it has to be right before configuration begins 

• Document numbering series: sequential numbering for invoices, purchase orders, goods receipts, and other core document types 

• Authorisation concept: who can approve what, at which value threshold, and which document types require a second sign-off 

• Document templates: layout and branding for invoice, purchase order, delivery note, credit memo, and any business-specific formats 

By the end of Week 2, the configuration blueprint is complete. This document becomes the instructions for Week 3. Any requirement not in the blueprint at this point goes on the Phase 2 list. 

Week 3: System Setup 

This is where SAP Business One Cloud comes to life. Ingold Solutions creates the company database on the SAP-certified Microsoft Azure HANA server — the production environment that will run the business from go-live onward. The configuration blueprint from Week 2 is applied systematically: chart of accounts, fiscal year definition, tax codes, posting periods, document numbering series, document templates, authorisation groups, banking and payment terms, and module-by-module configuration across every area confirmed in scope.  For German businesses, Week 3 also covers: 

• ELSTER configuration: setup for direct VAT advance return submission to the Finanzamt from within SAP Business One 

• DATEV export: journal entry export format configured for the external tax advisor — covers DATEV Lohn und Gehalt and LODAS interfaces where applicable 

• SEPA payment processing: payment wizard, payment methods, bank file generation, and SEPA creditor number setup 

• VAT ID validation: automatic VIES validation of EU business partner VAT numbers on accounts receivable invoices 

These are not optional extras in Ingold's German-market implementation process. They are standard configuration for any business operating in Germany — and they are configured in Week 3, not retrofitted six months after go-live.  By the end of Week 3, a fully configured SAP Business One Cloud environment exists. There is no real business data in it yet — but the architecture is ready, and the system passes a configuration review before Week 4 begins. 

Week 4: Data Migration 

This is the week that decides whether a go-live is clean or complicated.  Data migration is the process of extracting information from the current system — a legacy ERP, an accounting application, spreadsheets, or some combination of all three — and importing it into SAP Business One Cloud using SAP's Excel-based migration templates. The scope of what migrates depends on the implementation package. The Professional package (€4,900) includes both master data and opening balances import as standard. Standard and Plus tiers include configuration without data migration; many clients in those tiers elect to run a manual opening balance entry at cut-over. 

What gets migrated: 

• Business partner master data: customers and suppliers — names, addresses, contact details, payment terms, credit limits, GL account assignments 

• Item master data: product codes, descriptions, valuation method, sales and purchasing configurations, warehouse assignments 

• Price lists: customer-specific pricing, volume discount structures, currency variants 

• Opening balances: customer outstanding invoices, supplier outstanding payables, bank account balances, and general ledger account balances as of the cut-over date 

The data migration phase rewards preparation. A business that begins cleaning its data in Week 1 — removing duplicate suppliers, reconciling inventory records, standardising product codes — moves through Week 4 cleanly. A business that expects the migration process to clean the data for it is in for a difficult two weeks.  Ingold Solutions provides the migration templates and a data mapping document showing exactly which fields from the source system correspond to which fields in SAP Business One. The client team populates the templates; the Ingold consultant reviews them for completeness before import. Catching a mapping error before import takes minutes. Catching it after takes considerably longer. 

Week 5: User Training 

The best-configured SAP Business One Cloud system is only as useful as the people who know how to use it. Week 5 is structured training — not a demo, not a walkthrough of features, but hands-on practice in a test environment populated with the migrated data. Users process document types they will use in production from day one: a sales order created from a customer quotation, a goods receipt posted against a purchase order, a supplier invoice matched and posted, a financial report pulled and read. They make mistakes in a test environment where mistakes cost nothing, and they learn what happens when they do.  Training is organised by role: 

• Finance team: AP posting, AR management, bank reconciliation, financial reporting, period-end closing 

• Sales team: quotation creation, sales order management, customer contact records, CRM activity logging 

• Warehouse team: goods receipt posting, goods issue, inventory transfer, pick and pack where in scope 

• Management: dashboard configuration, KPI setup, executive reports, system-level queries and drill-down 

Training depth depends on the implementation package. Basic implementations include a 1-hour starter session and SAP Practical Handbook access. Standard and above include live expert-led training. The Professional package includes 5 hours of consultant-delivered training specific to the client's configured system and real migrated data — not generic software demos.  All users receive access to the SAP Learning Hub. Ingold provides role-specific quick reference cards for the document types each user will process daily. 

Week 6: Testing 

Testing is where the implementation proves itself — or where gaps surface before they have the chance to become go-live problems.  Three categories of testing run in Week 6: 

End-to-End Process Testing 

A complete business cycle is simulated, from order receipt to payment collected (order-to-cash) and from purchase request to supplier payment settled (procure-to-pay). Every step is processed by the users who will perform it in production, using the document templates and authorisation levels configured in Week 3. The aim is to confirm that the configured system matches the process blueprint signed off in Week 2. 

Integration Testing 

If SAP Business One Cloud connects to external systems in this deployment — a Magento or Shopify webshop, a banking interface via Multi Banking Connector, a third-party WMS, or an e-invoicing platform — those integrations are tested with live or near-live data. Orders placed on the webshop should appear as sales orders in SAP Business One. Bank statements should import and reconcile. Stock updates should flow bidirectionally. If any of this is not working cleanly, Week 6 is the time to find out — not Week 8. 

User Acceptance Testing 

The client's key users formally sign off each configured process. They confirm that the system does what the process blueprint described. Anything that does not match goes on the issue log, is prioritised, and is resolved before Week 7 begins. UAT sign-off from the client project lead is required before go-live preparation starts. 

Week 7: Go-Live Preparation 

No configuration changes happen in production during Week 7. Configuration is locked. What happens instead is the practical machinery of a clean launch: 

• Cutover date confirmed: the precise date and time when the old system switches off and SAP Business One Cloud becomes live. This is treated as fixed from this point forward 

• Final data migration run: opening balances and master data are re-extracted from the source system as of the cutover date and imported into the production environment. This is the definitive migration — it must be accurate to a single decimal place 

• User access activation: all production user accounts are created, tested, and confirmed. Named-user logins, licence types, and authorisation levels are verified for every user 

• Go-live checklist: a 30-point checklist covers every configuration item, every integration, every user access right, and every opening balance figure. Client project lead sign-off is required before go-live is approved to proceed 

• Hyper-care schedule: Ingold's support team publishes a daily check-in schedule for the first two weeks of production operation, including response time commitments for any issues raised 

The cutover date does not move in Week 7. If it needs to move, that conversation happens in Week 6. 

Week 8: Launch 

Go-live day is, in most implementations, considerably less dramatic than the team expected it to be.  The first purchase order is raised. The first customer invoice is posted. The first bank statement imports and reconciles. Everything works because Weeks 1 through 7 were done properly. And when something does not work exactly as expected — which occasionally happens, because production environments encounter edge cases that test environments do not — the Ingold support consultant is available that day to resolve it, typically within the hour.  What Week 8 actually looks like: 

• Days 1–2: first live transactions processed in production — every document type in scope is used in a real business transaction and confirmed 

• Days 3–5: finance team processes a full week of AP and AR in SAP Business One Cloud; management runs the first live management reports 

• End of Week 8: the business is running on SAP Business One Cloud. The old system moves to read-only mode for reference. The implementation is complete 

Post-launch support continues through a hyper-care period — typically two to four weeks — during which Ingold responds to queries within agreed response times and resolves any configuration gaps that surface during normal operation. 

Common Delays and How to Avoid Them 

Eight weeks is achievable. It is not guaranteed. The delays that push implementations to twelve or sixteen weeks are almost always the same ones — and almost all of them are preventable. 

Delay	Why It Happens	How to Avoid It
Data not ready on time	Businesses underestimate data-cleaning time. Duplicate records, inconsistent formats, and unreconciled balances are common.	Begin data preparation in Week 1. Assign one person to own the migration file. Review with Ingold before Week 4.
Scope added after sign-off	A process not in the original scope appears in Week 5 with a go-live deadline attached.	Anything added after Week 2 sign-off goes on a Phase 2 list. No scope changes in production setup.
Key decision-makers unavailable	Training skipped because the manager is travelling. Sign-off delayed because the FD is on leave.	Map decision-maker availability against the project calendar in Week 1. Block the dates.
Integration testing too late	Magento connector or banking setup not tested until Week 6 — too late to fix cleanly.	Test all external integrations by Week 5 at the latest. Ideally, smoke-test in Week 3.
Cutover date treated as flexible	Business communications go out, old support contracts end, staff plan around it. Then it moves.	The cutover date is fixed once confirmed. Treat it as a hard deadline from Week 7 onward.

 The pattern across all five is consistent: the problems that delay implementations are not technical. They are organisational. Good implementation partners manage the technical risk. Good clients manage the internal risk — availability, data readiness, decision-making authority. Both have to work. 

Which Implementation Package Covers Your Scope? 

The eight-week framework above reflects a Standard or Plus implementation. The scope of what is included — data migration, compliance configuration, training depth — varies by package. Reference the sapcloudone.de pricing page (updated April 2026) for the full package comparison:

What's Included	Basic	Standard	Plus	Professional
Full module installation	✔	✔	✔	✔
Company database + chart of accounts (SKR03/04)	✔	✔	✔	✔
Branded document templates	✔	✔	✔	✔
Starter training (1 hr + handbook + hub)	✔	✔	✔	✔
Live expert training sessions	—	1 hr	3 hrs	5 hrs
Banking + electronic payment config	—	—	✔	✔
ELSTER + DATEV export	—	—	✔	✔
Master data import (partners, items, prices)	—	—	—	✔
Opening balances import	—	—	—	✔
Price (excl. licences and hosting)	€500	€1,400	€2,950	€4,900

  Prices source: SAP partner market, April 2026. All packages include go-live support and SAP Learning Hub access.  The right package depends on two factors: how much data needs to move, and how much compliance configuration the business requires. For a German business with an established supplier and customer base, DATEV, ELSTER, and opening balances import — the Plus or Professional package — is almost always the appropriate starting point. 

Frequently Asked Questions 

How long does a standard SAP Business One Cloud implementation take? 

For a standard SMB implementation, six to eight weeks is achievable with full client engagement, clean data, and a well-scoped project. Simpler deployments — Basic package, limited customisation, no data migration — can go live in three to four weeks. More complex projects involving multiple warehouses, manufacturing modules, custom integrations, or significant data migration from a mature ERP typically run ten to sixteen weeks. The single biggest variable in timeline is data readiness, not configuration complexity. 

What does the Basic SAP Business One Cloud implementation package include? 

The Basic package at €500 covers full module installation, company database setup (chart of accounts SKR03/04, numbering series, authorisation concept), branded document templates (invoice, purchase order, delivery note, credit memo), a 1-hour starter training session, SAP Practical Handbook access, and SAP Learning Hub access. Banking configuration, DATEV/ELSTER setup, and data migration are not included — those are covered in the Standard (€1,400), Plus (€2,950), and Professional (€4,900) tiers respectively. 

What happens if the implementation runs over the planned timeline? 

Delays are almost always traceable to specific, identifiable causes: data not prepared on time, scope added after the configuration blueprint is signed off, or key decision-makers unavailable at critical sign-off points. Ingold Solutions manages this through weekly project status updates, a formal change request process for any scope additions, and an issue log reviewed at every project checkpoint. When a delay occurs, the impact on the go-live date is assessed and communicated immediately — not in the final week. Clients who manage data preparation and decision-maker availability on their side of the project rarely experience significant delays. 

Do I need to stop using my current system during the implementation? 

No. The implementation runs in a separate environment — a test company database on the Azure HANA server — until the cutover date. Your current business systems continue to operate normally throughout Weeks 1 through 7. On the cutover date, typically set at a month-end or financial period boundary, the old system moves to read-only mode for reference and SAP Business One Cloud becomes the live system. Most businesses retain read-only access to the old system for one to three months post-go-live for historical reference purposes. 

Does Ingold Solutions provide support after go-live? 

Yes. All implementation packages include go-live support, and every SAP Business One Cloud deployment through Ingold includes a hyper-care period of two to four weeks post-launch. During hyper-care, the support team responds to queries within agreed timeframes and resolves any configuration gaps that surface during normal operation. Ongoing support contracts are available beyond hyper-care, covering system maintenance, user additions, licence changes, and future configuration requirements as the business grows. 

Ready to Plan Your SAP Business One Cloud Implementation? 

Eight weeks from kick-off to go-live is realistic — with the right preparation, the right partner, and a realistic scope. If you would like Ingold Solutions to walk through what an implementation looks like for your specific business — by user count, data volume, compliance requirements, and any external integrations in scope — the conversation starts with a free consultation.  Ingold Solutions GmbH is an SAP Silver Partner and Microsoft Solutions Partner based in Berlin. ISO 9001 certified. Over a decade of SAP Business One Cloud implementations across 11 industry verticals. German-market compliance configuration — DATEV, ELSTER, SEPA, XRechnung — handled as standard, not as an add-on. Book a free implementation consultation  ·  Try SAP Business One Cloud free  ·  View implementation packages and pricing