- Home
- Services
- Data Migration
Architecture-led data migration
Large-scale data migration into Microsoft Dynamics 365
Architecture-led migration from legacy housing management systems. A structured, repeatable service designed for programmes of this scale, complexity and operational sensitivity.
Programme context
Focused on housing migration
Target platform: D365
Microsoft Dynamics 365 and Dataverse.
Crown Commercial: G-Cloud 15
Available through the Crown Commercial framework.
Incorporated: 2015
Lashan Digital brings architecture-led delivery experience to your programme.
What distinguishes us
Built for housing, built for D365
Data migration is one of Lashan Digital's key capabilities, delivered as part of our wider architecture-led digital, data and AI transformation services. We bring architecture, sector knowledge and platform expertise together in a single delivery team.
Architecture-led delivery
We resolve architectural decisions before mapping or build begins. Solutions Blueprint, Technical Specification and Impact Registers are produced and approved before development starts.
UK social housing knowledge
Our team understands how tenancy records relate to property hierarchies, how compliance cycles connect to assets, and how income and arrears data is structured. We know TSM, SDR, Awaab's Law, STAIRs and SAR requirements.
D365 platform expertise
Our engineers work directly with the Dataverse schema, including entity dependencies, GUID allocation, plugin behaviour and workflow suppression.
Customer experience focus
We consider the impact on tenants and residents alongside the technical migration: what customers see, what staff can act on, and what automated processes trigger once data is live.
Data migration, redefined
One platform for migration, integration and analytics
Our approach uses a single Data Intelligence Platform built on Databricks to handle migration, integration and analytics. Its five-layer architecture makes each record's transformation, governance and audit history traceable, whether it's a one-off migration load, a daily incremental sync or an analytics feed.
01
Source
Legacy systems
02
Ingest
Raw layer
03
Schema
Base layer
04
Transform
Enriched layer
05
Model
Curated layer
06
Load
D365 / Power BI
Migration methodology
How we build and how we run
Our methodology is structured and repeatable. It's flexible enough to accommodate the change that's inevitable in programmes of this duration and complexity.
01
Strategy & architecture
Scope, principles, target architecture and solution blueprint.
02
Discovery & profiling
Source profiling, data catalogue, inclusion and exclusion decisions, and classification.
03
Migration build
Mapping, transformation logic and iterative development and test cycles.
04
DQ & reconciliation
Source-to-staging-to-target counts, exception registers and sign-off.
05
Testing & dry runs
Technical and functional testing, followed by a full dry run against production-like data.
06
Cutover
Runbook-driven delivery with Go/No-Go gates and hypercare support.
In detail
Explore our approach
Data disposition strategy
We agree a data retention and archival strategy at the outset, informed by regulatory obligations and Data Owner sign-off. Some records need to be live in D365 on Day 1; others belong in an archive or need an agreed exclusion.
Migrate to target
Active records, open processes and live data needed from Day 1.
Archive to the right tier
Historical records, closed processes and regulatory retention.
Exclude with sign-off
Duplicates, corrupt data and out-of-scope records.
Three migration load types are maintained throughout: one-time historical loads, migrated once at cutover; ongoing incremental integrations, with daily or near-real-time syncs until cutover; and reference/configuration data, the static datasets that define the target system's vocabulary, loaded with GUID consistency across environments.
Proposed migration sequencing
Sequencing is domain-driven and respects entity dependencies. The property and asset hierarchy is always the anchor, because every other domain traces a reference back to it.
01
Discovery & architecture review
Agree scope and dependencies.
02
Assets & core reference data
Establish the property and asset hierarchy.
03
People, agreements & occupancy
Load records against their property references.
04
Repairs, voids, contracts & colleagues
Sequence operational domains by dependency.
05
Financials, cases & complaints
Load dependent financial and case records.
06
Documents & decommission
Complete document migration and legacy decommissioning.
Each stage has clear entry and exit criteria. Domain sequencing within each stage is determined by data dependency and operational risk, agreed during mobilisation.
Reconciliation & quality assurance
Formal reconciliation is performed at every layer. For every migration entity, structured workbooks compare counts and values across three checkpoints.
Source to staging
Row counts, extraction completeness and missing records.
Staging to target
Count match, exception register and value reconciliation.
GUID integrity
Every record retrievable via its parent GUID context.
Domain sign-off requires the Data Owner to formally review count matches, exception registers and value reconciliation before the domain is accepted as complete. Any unexplained differences are investigated and resolved.
D365 migration tooling
Our consultants work directly with the Dataverse schema and the platform tooling that D365 implementations depend on.
XRM Toolbox
Entity structures and metadata.
Advanced Find
Cross-reference validation.
ScaleUp / bulk tools
High-volume load operations.
Plugin Registration
Workflow suppression planning.
Power Automate
Process mapping and suppression.
Power BI + Dataverse
Reconciliation dashboards.
FetchXML & SQL
Post-migration validation.
Audit History
Change tracking confirmation.
Programme governance
Structured working cadence
We align to the governance structure within your programme and supplement it with collaborative working sessions at every level.
01
Programme Board
Monthly: senior stakeholders and strategic decisions.
02
Data Migration Steering
Fortnightly: progress, data quality and forward plan.
03
Cross-workstream interlock
Weekly: dependencies, prerequisites and stable releases.
04
Domain working sessions & architecture clinics
Weekly or as required: hands-on collaboration with Data Owners and SMEs.
Delivery model
A named team for the full contract term
We take end-to-end ownership as a single delivery partner, with a named team committed for the full programme duration. You have one accountable team across the workstreams. We operate either fully UK-based or as a hybrid onshore-offshore model depending on programme needs.
Programme Lead
Architecture, governance and escalation authority.
Data Migration Lead
Technical delivery across all domains.
Migration Developers
Package design, build and tuning.
Business/Data Analyst
SME facilitation and field-level mapping.
DevOps Engineer
Tooling, pipelines and environment configuration.
Reconciliation Engineer
Data quality dashboards and load progress reporting.
Planning a D365 data migration?
We'd welcome the opportunity to discuss your programme. Our approach is structured, transparent and built on direct delivery experience.