Fixed Asset Data Cleanup, Reconciliation & Conversion

A depreciation method. An in-service date. A useful life, a location code, a parent-child relationship. Each one reaches forward into the general ledger, the tax return, the audit binder and every future transaction against that asset. Move one carelessly and nothing breaks today — it breaks in year four, in front of an auditor, and the person who made the call is three jobs away by then.

Which is why I refuse to treat fixed asset data as a spreadsheet exercise. Mapping a field correctly means knowing what that field is for, and caring enough to ask the question before the load instead of after it.

What we do

Data work across the whole lifecycle, from one stubborn cleanup to a multi-entity conversion into Sage.

Conversion into Sage Fixed Assets

The real thing, run by us: Depreciation, CIP and Tracking, with accounting treatment, history and asset relationships intact. Sage Fixed Assets products are the platforms we load ourselves.
Conversion readiness for any platform

Headed somewhere other than Sage? We do everything up to the load — rules, mapping, cleanup, reconciliation, validation — so your implementer receives data that is genuinely ready.
Legacy-source reconstruction

Extract, interpret and rebuild data out of systems being retired, including the spreadsheet that quietly became a system of record while nobody was looking.
Data cleanup & normalization

Duplicates, orphans, creative naming conventions, mismatched codes, and the fields three different people populated three different ways.
Asset mapping & transformation

Map source structures to target structures on purpose, with the accounting and reporting consequence of each mapping said out loud.
Reconciliation

Tie the subledger to the general ledger, and the new register to the old one, with a documented explanation for every variance — including the awkward ones.
Mass asset changes

Apply lives, methods, classes, locations, hierarchies or ownership across large populations without leaving a crater behind.
Data validation

Rules-based checks on completeness, accuracy, consistency and plausibility before anybody calls a number final.
Acquisition & divestiture data work

Split, merge, transfer and re-establish asset populations as deals and restructurings move them around.
Pre- and post-load validation

Prove the data was right going in and still right coming out. It is the most-skipped step in this entire industry.
Reporting & exception analysis

Find the records that will cause trouble later, while they are still cheap and boring to fix.

What we load ourselves, and what we don't

Here is the honest boundary, because I would rather tell you now than mid-project. Hands-on conversion execution — the mapping, the load, the validation inside the product — is work we perform in Sage Fixed Assets Depreciation, CIP and Tracking. Those are the products I know down to the field level, and I am not going to pretend that is true of every system on the market.

For every other target platform, we do the work that actually decides whether a conversion succeeds: readiness, mapping rules, cleanup, reconciliation, and validation on both sides of the load — working alongside whoever is running it. Same rigour, different seat at the table.

Where conversions really go wrong

Conversions almost never fail on the technical load. They fail on the quiet decisions made during mapping: depreciation restarted instead of continued, accumulated depreciation dropped in as one lonely figure with no history behind it, tax and book treatment collapsed into each other, componentized assets flattened into a single record, in-service dates defaulted to the conversion date because the source was vague and the deadline was not.

Every one of those produces a register that loads beautifully, ties out at a summary level, and is wrong in a way that will not surface for years — right up until a disposal, an impairment or an auditor with time on their hands.

The defence is unglamorous and it works: decide the mapping rules out loud, write them down, validate on both sides of the load, and reconcile at a level of detail that would actually catch a problem. No heroics required.

How the work is staffed

Fixed asset judgment on the decisions, disciplined hands on the volume.

Subject-matter expertise

Every mapping and treatment call is made by someone who knows what the field does inside a fixed asset system — not by someone matching column headers and hoping.

Team-based execution

High-volume work runs as a team, so a large conversion never becomes a queue behind one tired person.

Project management

Milestones, dependencies and a plan built around your close calendar instead of colliding with it at the worst possible moment.

Quality review

Independent review of mapping, transformation and reconciliation before anything is handed back with the word final attached.

You will recognize your data in at least one of these

The subledger and the general ledger disagree, and the difference has become a tradition.
Assets live in the register that left the building years ago — or the reverse, which is worse.
A conversion is on the calendar and nobody has decided what happens to history.
Similar assets carry wildly different lives, classes or methods, depending on who set them up.
Every period, someone hand-adjusts a report before it is fit to send upstairs.
An acquisition or divestiture is about to move a large asset population, fast.

Common questions

Do you convert data into fixed asset systems other than Sage Fixed Assets?

No, and I would rather say it plainly than surprise you later. Actual conversion execution is Sage Fixed Assets Depreciation, CIP and Tracking. For any other target platform we do the readiness, mapping rules, cleanup, reconciliation and pre- and post-load validation, working alongside the team or partner running the load — which, honestly, is where conversions are won or lost anyway.

Should we clean fixed asset data before or during a conversion?

Both, in that order. Cleanup done beforehand is cheaper, calmer, and validated against a system you still understand. Anything that can only be resolved in the target structure gets handled during the conversion under written rules — never silently, never by whoever happens to be closest to the keyboard.

Can you work from spreadsheets rather than a system?

Yes, and spreadsheet registers are usually the most demanding source there is, 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 kept it alive. They almost always know more than they think they do.

How is depreciation history handled in a conversion?

That is a decision, not a default, and it belongs in scoping where you can still change your mind. Options run from carrying full period-level history to loading net book value with accumulated depreciation as an opening balance. Each one has consequences for reporting, tax and every future transaction, so the choice gets documented before a single record moves.

LET'S TALK

Bring us the data nobody wants to open.

The conversion, the cleanup, the reconciliation that has never tied out. One conversation is usually enough to work out what is really going on in there.

Talk Through Your Fixed Asset Data Explore the Health Assessment

Fixed Asset Consultant • Founded by Angela Bolton • angela@fixedassetconsultant.com

Related services

The problem showing up in one area often belongs to another. These are the adjacent engagements that most often turn out to be relevant.

FLAGSHIP DIAGNOSTIC

Fixed Asset Health Assessment

Diagnose the operating environment and establish the prioritized path forward before committing to a project, a system, or a remediation.

Explore

SAGE FIXED ASSETS

Sage Fixed Assets Consulting

Independent, business-side consulting for organizations whose Sage Fixed Assets environment is not delivering the result they expected.

Explore

SOFTWARE & IMPLEMENTATION

Software & Implementation Consulting

Decide what the environment should become before you automate it — then make sure the implementation actually delivers that.

Explore