Context
Through an Engineering for Change cloud-transformation fellowship, our principal served as digital-transformation consultant to a construction company making the jump from on-premises project systems to Autodesk Construction Cloud.
The problem
Construction data has gravity: drawings, RFIs, schedules, and site records accumulate in on-prem folders until every project answer requires the one person who knows where things live. Moving to cloud tooling is easy to want and easy to botch — migrations fail on sequencing, not software.
What we built
An end-to-end migration architecture: what moves, in what order, with what mapping into Autodesk Construction Cloud’s model — designed so field operations never stopped while the ground shifted under them.
Alongside it, a project-management dashboard for leadership: live project status pulled from the new platform, replacing the weekly phone-around.
Key decisions
Adoption-first sequencing: each migration phase had to leave users better off immediately, or the initiative would die the death of all half-adopted platforms.
Outcome
A sequenced path to the cloud and a dashboard leadership actually watched — digital transformation measured in changed behavior, not in licenses purchased.