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\u00a0actually open\u00a0SAP Business One Cloud\u00a0for the first time is the part that nobody explains in enough detail.<\/p>\n
This is that explanation.<\/span>\u00a0<\/span><\/p>\n 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 \u2014 the practical reality of what disciplined scope management, careful data preparation, and experienced configuration look like, week by week.<\/span>\u00a0<\/span><\/p>\n 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 \u2014 multiple warehouses, manufacturing modules, external system integrations, significant data migration \u2014 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.<\/span>\u00a0<\/span><\/p>\n \u00a0<\/span><\/p>\n Source: Ingold Solutions implementation\u00a0methodology, based on SAP’s Accelerated Implementation Program (AIP). Package prices per Ingold Solutions published rates, April 2026.<\/span><\/i>\u00a0<\/span><\/p>\n The first week of\u00a0a\u00a0SAP Business One Cloud implementation is not spent configuring software. It is spent listening.<\/span>\u00a0<\/span><\/p>\n A good discovery workshop does one thing that saves\u00a0significant time\u00a0later: it\u00a0establishes\u00a0the gap between what a business thinks it needs and what it\u00a0actually 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 \u2014 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.<\/span>\u00a0<\/span><\/p>\n What Ingold Solutions covers in Week 1:<\/span>\u00a0<\/span><\/p>\n 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 \u2014 it is the single most cost-effective step in any implementation.<\/span>\u00a0<\/span><\/p>\n With scope agreed, Week 2 goes deeper into the business processes that SAP Business One Cloud will\u00a0actually run.<\/span>\u00a0<\/span><\/p>\n 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\u00a0procure-to-pay cycle, the order-to-cash cycle, and financial period-end \u2014 and every business has its own way of doing the same things. The mapping exercise\u00a0identifies\u00a0where SAP’s\u00a0standard 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.<\/span>\u00a0<\/span><\/p>\n In Week 2, Ingold Solutions will also:<\/span>\u00a0<\/span><\/p>\n 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.<\/span>\u00a0<\/span><\/p>\n This is where\u00a0SAP Business One Cloud\u00a0comes to life.<\/p>\n Ingold Solutions creates the company database on the SAP-certified Microsoft Azure HANA server \u2014 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.<\/span>\u00a0<\/span><\/p>\n For German businesses, Week 3 also covers:<\/span>\u00a0<\/span><\/p>\n These are not optional extras in Ingold’s German-market implementation process. They are standard configuration for any business\u00a0operating\u00a0in Germany \u2014 and they are configured in Week 3, not retrofitted six months after go-live.<\/span>\u00a0<\/span><\/p>\n By the end of Week 3, a fully configured SAP Business One Cloud environment exists. There is no\u00a0real business\u00a0data in it yet \u2014 but the architecture is ready, and the system passes a configuration review before Week 4 begins.<\/span>\u00a0<\/span><\/p>\n This is the week that decides whether a go-live is clean or complicated.<\/span>\u00a0<\/span><\/p>\n Data migration is the process of extracting information from the current system \u2014 a legacy ERP, an accounting application, spreadsheets, or some combination of all three \u2014 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 (\u20ac4,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\u00a0elect\u00a0to run a manual opening balance entry at cut-over.<\/span>\u00a0<\/span><\/p>\n The data migration phase rewards preparation. A business that begins cleaning its data in Week 1 \u2014 removing duplicate suppliers, reconciling inventory records, standardising product codes \u2014 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.<\/span>\u00a0<\/span><\/p>\n 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\u00a0considerably longer.<\/span>\u00a0<\/span><\/p>\n The best-configured\u00a0SAP Business One Cloud\u00a0system is only as useful as the people who know how to use it.<\/p>\n Week 5 is structured training \u2014 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.<\/span>\u00a0<\/span><\/p>\n Training is organised by role:<\/span>\u00a0<\/span><\/p>\n\n\n
\n \u00a0<\/span><\/td>\n Phase<\/span><\/b>\u00a0<\/span><\/td>\n What Happens<\/span><\/b>\u00a0<\/span><\/td>\n<\/tr>\n \n Week 1<\/span><\/b>\u00a0<\/span><\/td>\n Discovery Workshop<\/span><\/b>\u00a0<\/span><\/td>\n Scope, process mapping, project plan,\u00a0user\u00a0and licence list<\/span>\u00a0<\/span><\/td>\n<\/tr>\n \n Week 2<\/span><\/b>\u00a0<\/span><\/td>\n Process Analysis<\/span><\/b>\u00a0<\/span><\/td>\n Configuration blueprint, chart of accounts, authorisation concept, document templates<\/span>\u00a0<\/span><\/td>\n<\/tr>\n \n Week 3<\/span><\/b>\u00a0<\/span><\/td>\n System Setup<\/span><\/b>\u00a0<\/span><\/td>\n Live company database built, all modules configured, compliance setup (ELSTER, DATEV)<\/span>\u00a0<\/span><\/td>\n<\/tr>\n \n Week 4<\/span><\/b>\u00a0<\/span><\/td>\n Data Migration<\/span><\/b>\u00a0<\/span><\/td>\n Master data, price lists, and opening balances imported and validated<\/span>\u00a0<\/span><\/td>\n<\/tr>\n \n Week 5<\/span><\/b>\u00a0<\/span><\/td>\n User Training<\/span><\/b>\u00a0<\/span><\/td>\n Role-based hands-on training in test environment with real migrated data<\/span>\u00a0<\/span><\/td>\n<\/tr>\n \n Week 6<\/span><\/b>\u00a0<\/span><\/td>\n Testing<\/span><\/b>\u00a0<\/span><\/td>\n End-to-end process testing, integration testing, user acceptance sign-off<\/span>\u00a0<\/span><\/td>\n<\/tr>\n \n Week 7<\/span><\/b>\u00a0<\/span><\/td>\n Go-Live Preparation<\/span><\/b>\u00a0<\/span><\/td>\n Cutover date locked, final data migration, user access activated, go-live checklist completed<\/span>\u00a0<\/span><\/td>\n<\/tr>\n \n Week 8<\/span><\/b>\u00a0<\/span><\/td>\n Launch<\/span><\/b>\u00a0<\/span><\/td>\n Live transactions processed, hyper-care support active, old system in read-only mode<\/span>\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Week 1: Discovery Workshop<\/span><\/b>\u00a0<\/span><\/h2>\n
\n
\n
\n
\n
\n
Week 2: Process Analysis<\/span><\/b>\u00a0<\/span><\/h3>\n
\n
\n
\n
\n
Week 3: System Setup<\/span><\/b>\u00a0<\/span><\/h3>\n
\n
\n
\n
\n
Week 4: Data Migration<\/span><\/b>\u00a0<\/span><\/h3>\n
What gets migrated:<\/span><\/b>\u00a0<\/span><\/h3>\n
\n
\n
\n
\n
Week 5: User Training<\/span><\/b>\u00a0<\/span><\/h3>\n
\n
\n
\n
\n