Closing or consolidating branches: what to do with branch records

Which branch records are at risk when a location closes?#

Branch records at risk are the ones that live only at the location: files, inboxes and paper that never reached the central ERP. In most multi-branch distributors the ERP holds orders, invoices and inventory for every branch, so leadership assumes history is safe. The gaps sit around the edges, in what counter staff, branch managers and drivers kept for themselves.

Those edge records often explain the central ones. A credit memo in the ERP says what was refunded; the branch manager's email thread says why the customer was angry and what the branch promised. When the location closes, the explanation leaves with the people unless someone collects it first.

• 1Counter and will-call records: pickup logs, signed pick tickets, cash drawer reconciliations and walk-in quote pads.
• 2Branch shared drives: local price sheets, special-pricing approvals, contractor job quotes, customer setup forms and bid files.
• 3Branch inboxes and group mailboxes: customer complaints, vendor back-order threads and delivery disputes.
• 4Warehouse records kept outside the WMS: cycle count sheets, damage photos, receiving discrepancy notes and hand-drawn bin maps.
• 5Delivery paperwork: signed delivery receipts, route sheets and driver notes filed at the dock.
• 6Local systems: a branch-only quoting tool, a standalone time clock or a camera recorder in the back office.

Branch closure checklist: the order that protects history#

A branch closure checklist protects history only if records are handled before access is removed, not after. The usual failure is sequencing: IT disables user accounts and cancels the branch circuit on the closing date, and the local server goes into storage with no one assigned to read it.

Run the record steps in parallel with the physical move of inventory and customers, and give each step an owner and a sign-off.

• 1Step 1: name a records owner for the closure, usually in operations or finance, separate from the person moving inventory.
• 2Step 2: list every system, drive, mailbox and paper location the branch used, including anything running on a local PC.
• 3Step 3: freeze deletion by pausing auto-delete rules on branch mailboxes and drives, and record any legal holds.
• 4Step 4: move open work, meaning open orders, back orders, open RMAs, customer balances and active ship-to accounts.
• 5Step 5: export closed history with branch and warehouse codes intact, plus a short data dictionary for each export.
• 6Step 6: collect local files from departing staff before their last day, including notebooks and phone photos of receipts.
• 7Step 7: set retention for each record type in the archive and record who is allowed to open it.
• 8Step 8: only then disable accounts, retire the local server and cancel branch-only subscriptions.

Move, archive or delete: a decision table for branch records#

Branch records fall into three groups: records the surviving branch needs to keep serving customers, closed history that should be archived as it was, and duplicates or personal files that can go once retention allows. Sorting them early keeps the ERP conversion small and the archive complete.

Treat the surviving branch's system as a place for live work, not a museum. Loading years of closed orders into it under a new warehouse code makes reports look continuous while quietly erasing which location actually served the customer.

Why merging branch history into the hub loses information#

Merging branch history into the surviving location loses the local context that explains it: which warehouse shipped, which salesperson quoted, which counter took the return. ERP conversions often remap old warehouse and branch codes to the new location so reports look tidy, and once that happens the original location cannot be recovered from the data.

That loss matters for more than record keeping. Inventory discrepancies, margin leaks and customer disputes are investigated by location. A distributor that later asks why a product line lost money in one territory needs the original branch, bin and user on each transaction.

The decision rule is simple. Keep the original branch and warehouse identifiers as fields on every archived record, and keep a crosswalk table that maps old customer, item and warehouse codes to their new equivalents.

Choosing an archive format before the lease ends#

The archive format decides whether closed branch history can still be read once the people who knew it are gone. A read-only copy of the old database keeps everything but needs software and a login to open; flat exports with a data dictionary are easier to keep but can miss attachments and notes.

Check what your ERP's standard export actually covers. Oracle's NetSuite help, for example, says the Full CSV Export does not currently export all data, which is why teams on NetSuite often add saved search exports or other extraction routes for transaction detail. Other ERPs have their own limits, so compare record counts against the live system before decommissioning anything.

Illustrative: an industrial distributor folds two branches into a hub#

Illustrative: a fictional industrial and electrical supply distributor closes two small branches and moves their customers to a regional hub. All three locations run the same ERP, so the IT lead plans to remap the closed branches' warehouse codes to the hub and cancel the branch circuits on the closing date.

The COO pauses that plan after a records walk-through. The branches hold years of counter tickets, a shared drive of job quotes for contractor customers, and a manager's mailbox full of back-order disputes with one large vendor. The team moves open orders and active accounts to the hub, exports closed history with the original branch codes, copies the drives read-only and boxes the counter paper with an index before staff leave.

Months later, a contractor disputes a large return processed at one of the closed branches. The team finds the original quote, the signed pick ticket and the branch manager's email in the archive the same day, and the dispute closes without a credit. The archive also becomes the starting point for the company's first full records inventory.

Retention, holds and who owns the archive#

Retention for a closed branch's records follows the same rules as the rest of the company: tax, contract, warranty, claims and employment periods, whichever is longest for each record type. The closure does not shorten any of them, and an open dispute or claim puts a hold on related records until counsel releases it.

Name an owner for the archive after the branch is gone. Archives without an owner tend to be deleted in the next storage cleanup or left on a server that no one can log into. Employee files from the branch belong with HR, not in the operational archive.

How SourceX approaches closed branch history#

SourceX treats a closed branch's operating history as one record family within a wider company inventory, not as a separate project. Order exceptions, return reasons, back-order threads and inventory discrepancy notes show how distribution work actually gets resolved, which is the kind of record AI developers look for. Data is licensed, not sold, and the company keeps ownership.

Assessment follows the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The first fit check uses metadata only, such as systems, years covered and record types, so nothing leaves the archive during the initial assessment, and customer and employee details are removed before anything is considered for delivery.