Every fixed asset system implementation contains an optimistic moment. Someone says: once we are in the new system, the data will be clean.
It will not. A system conversion is a transfer, not a treatment. Whatever goes in comes out the other side — same errors, same gaps, same undocumented decisions, now blessed by a new platform and considerably harder to question.
What legacy fixed asset data usually contains
After enough conversions, the inventory of problems is remarkably consistent:
- Assets that no longer exist. Ghost assets from disposals never recorded, often 5-15% of line count in an environment without a disposal trigger.
- Descriptions that identify nothing. "EQUIPMENT," "2014 ADDITIONS," "VARIOUS." No serial, no location, no tie to anything physical.
- Bulk lines hiding many assets. One row for a $2.4M rollout across nineteen sites. Unretirable, untransferable, unverifiable.
- Lives applied by habit. Whatever the default was when the prior system was configured, applied ever since regardless of asset type.
- Book and tax that no longer agree. Two registers maintained in parallel and reconciled once a year with adjustments nobody can now explain.
- In-service dates equal to invoice dates. Convenient, common, and wrong — with knock-on effects through depreciation and tax.
- Accumulated depreciation that does not tie. The sub-ledger and the general ledger differ by an amount that was plugged years ago.
Why implementations skip the cleanup
Not out of ignorance. The pressure is structural.
A software implementation is scoped, budgeted, and staffed around configuration and go-live. Data cleanup has no natural owner in that scope: the vendor's job is to load what you give them, and the internal team is already absorbing the project on top of a full-time role. Cleanup is the one workstream with no deadline of its own, so it is the one that gets deferred.
Then go-live arrives, the balances tie to the old system — which is the acceptance test — and the errors are now baseline. Nobody will revisit them, because revisiting them means explaining why the numbers in the new system are changing.
What clean conversion actually involves
- Profile before you plan. Count nulls, duplicate serials, zero-cost assets, fully depreciated assets still active, assets with in-service dates predating the entity. You cannot scope the work until you know its shape.
- Reconcile the sub-ledger to the GL first. If they do not tie before conversion, they will not tie after — you will have imported an unexplained difference.
- Attack ghost assets with a targeted verification. Not a wall-to-wall inventory. Sample by class and location, extrapolate, and verify the high-value populations directly.
- Decompose bulk lines by materiality. The large ones are worth breaking apart into real assets with real locations. The immaterial ones can carry forward with a documented rationale.
- Rebuild the life and class mapping deliberately. Conversion is the one moment when reclassifying is cheap. After go-live it is a change with an audit trail and an explanation attached.
- Fix book/tax divergence at the source. Land both registers from a reconciled position instead of importing the historical gap.
- Document every decision. The rationale for each rule is what makes the resulting register defensible to an auditor two years from now. Undocumented cleanup looks identical to an unexplained adjustment.
The consulting part is not optional
The reason this work needs judgment rather than a mapping spreadsheet is that most conversion decisions are not technical. Whether a bulk line gets decomposed, whether a class gets re-lived, whether an unverifiable asset gets written off — each is a judgment about materiality, audit exposure, and how the register will be used. A data migration specialist cannot make those calls. Someone who understands the accounting consequences has to.
Clean data also depends on the naming and identity work upstream. If projects and assets have no consistent identity to begin with, cleanup has nothing to group on.
A new fixed asset system is a genuine upgrade in control, reporting, and effort. It is not a filter. Whatever is loaded on day one is what the organization will be reporting from for the next decade — so day one is the moment worth spending on.