SAP Business One Decommissioning Done Properly

SAP Business One decommissioning is the process of fully retiring a B1 deployment — returning licences to SAP, shutting down the underlying SAP HANA or Microsoft SQL Server database, ending SAP Partner Edge support retainers, and releasing infrastructure — while preserving the historical data, customisation catalog, and compliance evidence in a long-term archive. SMBs typically consider B1 decommissioning after a successful migration to Oracle Fusion (or another successor ERP), or when an M&A event has consolidated the B1 entity onto a parent system. The trigger is usually a CFO realising the 'compliance-only' B1 instance is consuming $40K–$200K/year for one or two quarterly auditor queries — and asking 'why are we still paying for this?'.

Typical year-one savings range $40K–$200K for small single-company SMBs and $200K–$800K for multi-company or partner-supported B1 instances. Breakdown: B1 named-user licence annual maintenance ($95–$135/user/year, often locked in at original user counts even after migration); HANA Runtime Edition or SQL Server Standard licensing ($10K–$40K/year); infrastructure (app + DB + Service Layer + dev/test, $15K–$60K/year cloud or amortised on-prem); SAP Partner Edge partner support retainer ($12K–$60K/year for most SMBs); part-time admin/DBA labour ($30K–$80K/year fully loaded). Decommissioning eliminates all of these — replaced by a Syntra archive subscription typically $8K–$30K/year. Net year-one saving: 60–90% of current B1 TCO.

Six phases over 8–12 weeks: (1) Pre-decommission archive — full B1 data, customisation, and report archive built and validated; (2) Compliance sign-off — finance, audit, legal sign off that archive satisfies IRS/HMRC/GoBD/CGI/SDI retention; (3) Historical reporting cutover — internal and external reporting users moved from live B1 to archive query interface; (4) Read-only freeze — B1 set to read-only, monitored for unexpected access for 2–4 weeks; (5) Licence and support termination — SAP licence return notification, SAP Partner Edge support contract termination per termination-clause notice period; (6) Infrastructure shutdown — DB and app tiers shut down, backups retained per policy, environments deprovisioned. Each phase has a sign-off gate.

Most SMB B1 instances are supported by an SAP Partner Edge partner under a multi-year retainer contract — typically $1K–$5K/month with 3-month or 6-month termination notice. SMBs decommissioning B1 need to plan around this notice period: termination notice should be filed at the start of the read-only freeze phase so the contract ends naturally as decommission completes. Some partner contracts include early-termination penalties or knowledge-transfer obligations — Syntra ETL's pre-decommission archive includes a customisation inventory that satisfies typical knowledge-transfer requirements (every UDF, UDO, add-on, Crystal Report documented). SAP licence return notification is a separate workflow filed with SAP directly, not the partner.

Everything is preserved in the archive's customisation catalog. Discovery during archival enumerates every UDF (via CUFD), every UDO (via OUDO), every registered SDK add-on, every Service Layer add-on, every Crystal Report, every B1 Studio dashboard, every Formatted Search, every PLD layout. The catalog includes source/binary artifacts where available, metadata (name, business owner, last-used date), and a Fusion-equivalent disposition note. After decommissioning, this catalog is the evidence layer: a future auditor asking 'what custom logic was running in your B1 environment in 2021?' gets a complete answer from the catalog. For SDK add-ons under active partner support, you may need to formally terminate add-on subscriptions separately from the base partner support contract.

Yes — that's the whole point. The Syntra archive's SQL (JDBC/ODBC) and REST interfaces remain fully operational after B1 decommissioning. Internal finance, internal audit, external auditors, tax authorities, and customer-service reps can query archived OINV, OPCH, OJDT, OCRD, OITM data exactly as they would have queried live B1 — same table names, same column names, same UDF fields, same multi-branch and multi-currency context. Query performance is typically faster than live B1 was (columnar Parquet storage, partitioned by fiscal year). Tax-authority and statutory-audit access patterns (GoBD evidence pack, SDI XML retrieval, IRS-format extracts) are pre-built. Decommissioning eliminates B1; it doesn't eliminate access to B1 data.

Decommissioning the live B1 system doesn't end GDPR obligations on the underlying personal data — it just moves the responsibility to the archive. Syntra's archive supports GDPR right-to-erasure: a request to erase a specific data subject's personal data triggers nullification of PII fields on the relevant OCRD/OCPR rows (CardName if person-name, contact name/email/phone, bank account, tax ID where stored) while preserving aggregate financial integrity. The related OINV/OPCH/OJDT rows remain intact (legally required for tax retention) but no longer carry the personal-data fields. An erasure evidence log is written documenting the request, the fields nullified, and the timestamp — auditable evidence that the request was processed in compliance with GDPR Article 17.

Three scenarios where keeping B1 alive may make sense, at least temporarily. First: a hybrid setup where one entity is staying on B1 because of a vertical-specific add-on (manufacturing MES integration, retail POS) that doesn't have a Fusion equivalent — in that case keep the relevant B1 instance, but archive the migrated entities. Second: an active customer-data project that's still in flight using live B1 (e.g. a portal that pulls from B1 Service Layer) — finish the project first, then decommission. Third: a regulatory or contractual requirement that explicitly mandates a 'live' source system rather than an archive — rare, but found in some pharma, defence, and government-contracting contexts. In all other cases, decommissioning post-migration is the rational choice and saves substantially on TCO.