Accounting Firms: Handling Client Ledgers Trapped in Lotus 1-2-3

TL;DR

Client archives still contain historical general ledgers, depreciation schedules, payroll summaries, and inventory reconciliations created in Lotus 1-2-3. Uploading those files to a free converter risks confidentiality and independence rules. Local conversion to XLSX, PDF, and CSV is the defensible default for CPAs, advisory firms, and litigation-support teams.

Why accountants still see Lotus

Long-standing clients hand over storage drives, off-site backup tapes, or restored bookkeeper laptops with decades of ledgers. Many of those workbooks were created in Lotus 1-2-3 before Excel became the firm-wide standard, and they survived simply because nobody had the time—or the right tool—to migrate them.

Engagements that surface these files include estate work, business valuations, IRS examinations, internal control reviews, M&A diligence, and litigation support.

Why "free online converter" is not an option

Confidentiality rules from the AICPA, state boards, and engagement letters do not contain a "but it was a free tool" exception. Uploading a client ledger to an unknown server can implicate independence, confidentiality, and data-sovereignty obligations all at once.

A desktop converter that runs entirely on a partner or staff workstation is the path of least regulatory friction. Files stay inside the firm environment, and the conversion log becomes part of the workpapers.

A defensible conversion workflow

1. Stage a read-only client copy

Mount the client archive read-only and copy the Lotus folder structure into an engagement-specific location on a firm workstation. Never convert against the original media.

2. Convert to XLSX, CSV, and PDF

Use XLSX for ledger review and recalculation, CSV for transaction-level analytics, and PDF for workpapers. Run the conversion in batch—per year, per entity, or per system.

3. Preserve a conversion log

Save a per-file log with source path, output path, format, and timestamp. Attach it to the engagement workpapers so any reviewer can reproduce the conversion.

Spot checks before you trust the output

For each major ledger, verify totals, currency formatting, period dates, and a small handful of formulas in the converted XLSX. Confirm hidden sheets and named ranges have not been silently dropped.

When something looks off, prefer to re-convert with an updated extension rather than editing the output by hand. The audit trail is cleaner that way.

Make legacy ledgers a billable advantage

A firm that can ingest and review Lotus archives quickly turns a client headache into a billable specialty. Standardize the workflow once, and every engagement that includes legacy spreadsheets becomes a smoother, faster project.