Decades of project data,
moved without touching it.

Al Ghurair operates across real estate and construction, where a single project runs for years and carries a long tail of contracts, variations, certificates and invoices. That history has value: it is what project invoicing and cost tracking are calculated from.

Construction accounting is unusually unforgiving. Revenue is recognised against progress, retention is held back, and a contract's financial position depends on records going back to its start. You cannot begin at zero.

The legacy data was too large to load by hand and too important to load carelessly. Manual entry at that volume guarantees errors, and errors in project financials surface months later as disputes with clients or subcontractors.

It also could not be a one-time script. Data arrived in batches over the course of the migration, so whatever we built had to be re-runnable, idempotent and auditable rather than a single irreversible import.

• R1Bulk legacy project data imported into Dynamics 365 F&O
• R2Processing through batch utilities rather than manual entry
• R3A repeatable pipeline that could be re-run as further data arrived
• R4Project invoicing operational on the migrated history
• R5Traceability, so any imported record could be tied back to its source

We built an Azure-based pipeline to stage, transform and load the legacy data, then processed it inside the ERP through batch utilities — so the heavy lifting happened outside the ERP and the ERP only ever received clean, validated records.

Why a pipeline rather than an import: a one-off import gives you a single chance to be right. A pipeline can be run, checked, corrected and run again — which is the only realistic way to move project financials that people will later be audited against.

• 01Azure pipeline. Staging and transformation of bulk legacy project data outside the ERP.
• 02Batch processing. Imported records processed through Dynamics 365 batch utilities rather than by hand.
• 03Project invoicing. Invoicing brought into operation on top of the migrated project history.
• 04Repeatability. The pipeline built to be re-run as additional legacy data was released.
• 05Reconciliation. Imported records traceable back to source for checking and audit.