We need to clean up fifteen years of messy historical customer data in our legacy database before we can migrate to our new system and prepare for due diligence. This Legacy Data Migration seat is incredibly tedious, and absolutely nobody on our current team wants to own it. How do we solve this?

Question

Tyler Smith · Accepted Answer

When you have a critical, temporary seat that no current team member wants, you cannot force it on someone who fails the GWC™ test. Doing so guarantees poor execution and resentment. Instead, you must treat this as a structural capacity problem. First, define the Legacy Data Migration seat on your Accountability Chart with clear, outcome-based roles. These should include auditing historical records, mapping data fields, and verifying migration accuracy. Once the seat is defined, look outside your current leadership team. Because this is a tedious, highly specialized task, the best solution is to hire a fractional contractor or a specialized data-cleansing agency to own this seat. They will have the tools, the capacity, and the actual desire to do the work. The external contractor will temporarily hold the seat on your Accountability Chart and report directly to your Head of Technology or Head of Operations. Alternatively, you can automate large portions of the migration process using specialized data-parsing tools. In that case, you must assign the oversight of those automated tools to an existing seat that has the capacity and technical capability to manage them. Whichever path you choose, the key is keeping the seat distinct on your chart. Do not let the tedious nature of the work lead to a lack of accountability, as clean historical data is vital for passing buyer due diligence during an exit.