// Source System
Access Dimensions to Dynamics 365 Data Migration
We've moved nominal, sales and purchase ledger data out of Access Dimensions into D365 F&O — cleanly, completely, on time.
ACCESS DIMENSIONS — Entity Mapping
// The Challenge
Why Access Dimensions migrations are hard.
Access Dimensions is common among UK SMEs and mid-market businesses, and compared to larger ERPs its data model is relatively straightforward — a Nominal Ledger, Sales Ledger and Purchase Ledger with analysis codes for basic departmental reporting. The migration challenge is usually less about structural complexity and more about years of manual workarounds: journals posted to suspense accounts, ad-hoc analysis code usage, and customer/vendor records that were never properly closed off.
Because Access Dimensions installations are often smaller in data volume than the other systems we migrate from, the priority shifts from performance and staging strategy toward thorough cleansing — this is frequently the source system where our Data Cleansing & Enrichment service adds the most value before migration.
Where a business has grown through acquisition, it's common to find multiple Access Dimensions company databases that need consolidating into a single D365 legal entity, each with its own chart of accounts variations to reconcile.
// Mapping
Access Dimensions entities, mapped to D365.
| Source entity | D365 entity |
|---|---|
| Nominal Ledger — Account codes | MainAccount |
| Sales Ledger — Customer accounts | CustTable |
| Purchase Ledger — Supplier accounts | VendTable |
| Analysis codes | Financial dimensions |
// Pitfalls
Where Access Dimensions migrations go wrong.
- Years of manual workarounds (suspense postings, inconsistent analysis code use) are common — budget for cleansing, not just mapping.
- Multiple company databases from acquisitions often need consolidating into one D365 legal entity — reconcile chart-of-account variations early.
- Customer and vendor records that were never closed off tend to accumulate — a Health Check before migration usually pays for itself here.
- Smaller data volumes mean the real risk is data quality, not extraction performance — plan the workstream accordingly.
// Domains
Domains we most commonly migrate from Access Dimensions.
// Methodology
The same six phases, every time.
01
DISCOVER
Profiling, volumes, quality scoring across every source system in scope.
02
DESIGN
Source-to-target mapping and the cleansing plan, agreed before build starts.
03
BUILD
DMF templates, KingswaySoft packages, SQL staging tables.
04
TEST
Two mock migrations, full reconciliation, and UAT sign-off.
05
CUTOVER
Final load, balance reconciliation, go-live clearance.
06
STABILISE
Corrections, closure report, retainer option for what follows.
// FAQ
Questions about migrating from Access Dimensions.
Structurally, yes — but data quality issues from years of manual workarounds are common, so cleansing is often the bigger workstream.
Planning a Access Dimensions to D365 migration?
Start with a Health Check to see exactly what needs cleansing before it moves.