Systems and records
SAP Business One data archive: what it removes and what to save first
By SourceX Editorial · Updated
Short answer
The SAP Business One data archive permanently removes closed documents and their transaction detail up to a cutoff date, to shrink the company database. Balances and open items stay, but document-level history for those years does not. The rule: before any archive run, take a full copy of the database and attachments folder and prove it restores.
Key takeaways
- Despite the name, the B1 data archive deletes closed history from the live company rather than moving it to a searchable store.
- Balances and open items survive an archive run; closed documents and their detail for archived years do not.
- A restorable full copy of the database and attachments folder is the only way back after an archive run.
- Slow reports and large backups have alternatives that do not delete history.
- Before moving off B1, migrate open items and balances and keep the full old database as a reference.
What does the SAP Business One data archive do?#
The SAP Business One data archive is a wizard that permanently deletes closed transactions from the company database up to a cutoff date you choose. Companies run it to shrink a database that has grown large or slow after years of quotes, orders, deliveries, invoices and journal entries.
The word archive misleads people. The wizard does not move records into a separate store that users can still search inside the live company; it removes them while keeping balances so the books still agree. Unless someone saved a restorable copy beforehand, the document-level history for those years is gone.
Typical triggers are slow reports, long backups, a server move or an upgrade. Each has alternatives, so an archive run should be a decision the CFO approves, not routine maintenance.
What it removes and what it keeps#
An archive run removes closed, fully processed documents and their detail for the periods you select, and keeps what is still open or needed for balances. SAP's guide for your release lists exactly which objects qualify and under what conditions, so treat the table as a planning aid and check the guide before acting.
| Item | Typical effect of an archive run | What to save first |
|---|---|---|
| Closed sales and purchasing documents | Removed from the live company up to the cutoff | Full database backup plus document-level exports |
| Journal entry detail for archived periods | Summarized so that balances still agree | Detailed general ledger reports by period |
| Open documents and unreconciled items | Kept | Nothing extra |
| Account and business partner balances | Kept | Trial balance and aging reports at the cutoff, for later reconciliation |
| Items and business partners | Generally kept as master data; confirm in your release's guide | Master data lists including history-related fields |
| Inventory movement detail | Detail for archived periods may be reduced; check your version | Inventory audit and valuation reports |
| Attachments on archived documents | Links to removed documents are lost even if files stay on disk | A copy of the attachments folder mapped to document numbers |
| User-defined fields on archived documents | Removed with the document | Exports that include those fields |
Why save a full copy first?#
A full copy first is the only reliable way to keep the history an archive run deletes. Report exports capture what someone thought to export; a database backup captures everything, including user-defined fields, add-on data and links nobody has thought about yet.
Keep the copy away from the B1 server, assign someone to own it and decide how long it must be kept. A backup on the same machine, overwritten by the next nightly job, does not count.
- A full backup of the company database from Microsoft SQL Server or SAP HANA, taken with users logged out.
- The attachments folder and any picture, template or report folders set in the general settings paths.
- Add-on data held in user-defined tables or separate databases.
- A note of the B1 version and patch level, so the backup can be restored later.
- A test restore into a separate company, checked by opening old documents and running a trial balance for an archived period.
Which problems have alternatives to archiving?#
Most reasons for archiving have fixes that keep the history. Work through them with your B1 partner before anyone runs the wizard.
Database size is often blamed for problems that come from elsewhere: an undersized server, a report written against every transaction instead of a date range, or attachments stored inside backup sets. Measure where the time goes before deciding that history is the problem.
| Problem | Try first |
|---|---|
| Slow reports and queries | Index and query tuning, or reporting against a copy of the database |
| Large or slow backups | Backup compression, moving attachments to separate storage, a storage review |
| Upgrade or server move | Plan the upgrade on the full database and confirm with your partner whether size is really the obstacle |
| Migration to a cloud ERP | Migrate open items and balances, keep the old company read-only or exported |
| Hosting or license cost | Review user licenses and hosting before deleting history |
Illustrative: a packaging manufacturer stops an archive run#
Illustrative: a fictional packaging manufacturer has run SAP Business One for many years. Reports have slowed, and the IT lead proposes archiving the oldest years before an upgrade.
The CFO asks what would be lost. The list includes closed sales orders and deliveries linked to customer quality complaints, purchase history used in supplier reviews, and returns with free-text reasons in user-defined fields. None of it is needed daily, but all of it is needed when a customer disputes a recurring defect.
The company takes a full database backup and copies the attachments folder, restores both into a test company and confirms old documents open. It then tunes the slow reports instead of archiving, and keeps the full copy as a reference for a later ERP move and a possible review of its order and quality history.
What should the CFO confirm before approving an archive run?#
The CFO should approve an archive run only after five questions have clear, written answers. If any answer is unknown, the run waits.
Write the answers into a one-page approval with the cutoff date, the backup location and the names of whoever restored and checked it. If a customer, auditor or buyer later asks what happened to the older documents, that page is the answer.
- Is a verified, restorable full copy stored away from the B1 server?
- Have the auditors and tax advisers confirmed that records you must keep for archived years will still be available?
- Are there open disputes, warranty claims or audits that need document-level history?
- Has anyone assessed whether the history has reuse value, such as analytics or licensing?
- Is the cutoff date documented and approved?
How SourceX looks at Business One history#
SourceX looks at old B1 history as a possible record set, not clutter. Quote-to-order chains, deliveries, returns and their notes show how a manufacturer or distributor handled real orders and exceptions, which is the kind of operational record AI developers license.
The starting point is a description, not data: under the Supply step of the SourceX five-step transaction, a company describes its B1 version, years of history and record families, and nothing is shared. The SourceX Enterprise Data Value Framework then helps judge whether the history is worth preparing. None of that is possible once the history is deleted, which is why the copy comes first.
Frequently asked questions
Can archived SAP Business One data be restored?
Not inside the live company. Once an archive run completes, the removed documents are gone from that database. The only way back is a backup taken before the run and restored into a separate company, which is why the backup must be tested before archiving, not after.
Do financial reports for old years still work after archiving?
Balance-based reports should still agree, because balances are preserved. Reports that depend on document detail, such as sales by item or by customer for archived years, will no longer show that detail. Run and save the reports you need for those years first.
Is a database backup enough, or do we need exports too?
A tested backup is the foundation, because it keeps everything. Exports to CSV or a separate database still help people look up old history without restoring a B1 company, and they make any later migration or licensing review easier. Keep both, linked by document numbers.
Should we archive before moving to a new ERP?
There is rarely a good reason to. A move to a new ERP is a chance to migrate open items and balances and keep the old database as a reference. Deleting history first removes options for audits, disputes, analysis and licensing while saving little.
How long should we keep the pre-archive copy?
As long as your retention obligations and business needs require, which your accountant and counsel can confirm for each record type. Write the retention period on the backup record, and recheck that the restore works whenever the server or the B1 version changes.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.