Fixed asset data is not just rows and columns. Every field can carry accounting, reporting, system and lifecycle consequences.
A depreciation method, an in-service date, a useful life, a location code, a parent-child relationship: each one is a decision with downstream effects on the general ledger, on tax, on reporting, and on every future transaction against that asset. Move them incorrectly and the error is not visible until it is expensive.
That is why fixed asset data work is a subject-matter problem before it is a technical one. Mapping a field correctly requires knowing what the field is for.
Data work across the full lifecycle, from a single cleanup to a full multi-entity conversion.
Move fixed asset data into a new system with the accounting treatment, history and relationships intact.
Extract, interpret and reconstruct data from systems that are being retired — including spreadsheets that became systems of record.
Resolve duplicates, orphans, inconsistent naming, mismatched codes and fields that were never populated consistently.
Map source structures to target structures deliberately, with the accounting and reporting consequences of each mapping made explicit.
Tie the subledger to the general ledger, and the converted register to the source register, with documented explanations for every variance.
Apply lives, methods, classes, locations, hierarchies or ownership changes across large populations without collateral damage.
Rules-based validation of completeness, accuracy, consistency and plausibility before anything is treated as final.
Split, merge, transfer and re-establish asset populations through transactions and restructuring.
Prove the data was right before the load and still right after it — the step most often skipped.
Exception reporting that finds the records that will cause problems later, while they are still cheap to fix.
Conversions rarely fail on the technical load. They fail on decisions made quietly during mapping: depreciation restarted rather than continued, accumulated depreciation loaded as a single figure with no history behind it, tax and book treatment collapsed into one, componentized assets flattened into a single record, or in-service dates defaulted to the conversion date because the source was ambiguous.
Each of these produces a register that loads cleanly, reconciles at a summary level, and is wrong in a way that surfaces one, two or five years later — usually during an audit, a disposal, or an impairment.
The defence is boring and effective: decide mapping rules explicitly, document them, validate on both sides of the load, and reconcile at a level of detail that would actually reveal a problem.
Fixed asset expertise on the decisions, disciplined execution on the volume.
Every mapping and treatment decision is made by someone who knows what the field does in a fixed asset system, not by someone matching column headers.
High-volume work is executed by a team, so a large conversion does not become a queue behind one person.
Defined milestones, dependency tracking, and a plan that accounts for the close calendar rather than colliding with it.
Independent review of mapping, transformation and reconciliation before results are handed back as final.
Both, in that order. Cleanup done before the conversion is cheaper, lower risk, and validated against a system you still understand. Anything that can only be resolved in the target structure is handled during the conversion under documented rules — never silently.
Yes. Spreadsheet-based registers are common and are usually the most demanding source, because the rules that governed them were never written down. The work starts by reconstructing those rules from the data itself and confirming them with the people who maintained it.
That is a decision, not a default, and it belongs in scoping. Options range from carrying full period-level history to loading net book value with accumulated depreciation as an opening balance. Each has consequences for reporting, tax and future transactions, and the choice is documented before any load.
Bring the conversion, the cleanup, or the reconciliation that isn't tying out. A short conversation is usually enough to establish what is really going on.
Fixed Asset Consultant • Founded by Angela Bolton • angela@fixedassetconsultant.com
The problem showing up in one area often belongs to another. These are the adjacent engagements that most often turn out to be relevant.
Diagnose the operating environment and establish the prioritized path forward before committing to a project, a system, or a remediation.
ExploreDefine the future operating environment before automating or migrating it — then make sure the implementation delivers it.
ExploreIndependent, business-side consulting for organizations whose Sage Fixed Assets environment is not delivering the result they expected.
Explore