Beyond the Migration Plan: Why Relationships Drive Content Modernization
Content modernization is a relationship challenge
Content migration is often framed as a technical step in modernization: move pages out of legacy sites, implement them on a new platform, and decommission what’s old. But in practice, content migration and modernization lives or dies on something far less technical: relationships.
Legacy content exists because people rely on it. It reflects years of policy decisions, operational constraints, and institutional knowledge. When that content moves to a modern platform, the work can’t succeed without the active involvement of the people who own, maintain, and depend on it.
At the same time, those relationships are rarely uniform. Some program offices want to modernize the content themselves. Others need significant support or want little involvement. Capacity can shift over time. And priorities can change mid-migration.
Content migration and modernization efforts that assume a single engagement model struggle. But those that treat it as a flexible partnership with shared standards and adaptable ownership are far more resilient.
How inflexible approaches derail content migration
Many content migration and modernization projects kick off with well-defined plans, fixed roles, and standardized workflows. While clarity has value, rigidity often becomes a liability when working with legacy content. Common failure patterns include:
- Starting with tasks instead of trust: When migration begins with spreadsheets, deadlines, and review requests instead of first building relationships, program teams may feel overwhelmed, defensive, or unclear about why changes are needed. This slows reviews and increases resistance.
- Assuming consistent capacity: Program offices rarely have stable availability. Staff turnover, policy changes, and operational demands can suddenly limit participation. Rigid processes and models break when teams can’t engage as originally planned.
- Enforcing one way of working: Some teams want to audit and write their own content. Others prefer external drafting with internal review. Forcing a single model creates bottlenecks and frustration—especially when it doesn’t match how teams already work. These issues are not caused by lack of expertise or effort. They arise when content migration and modernization are treated as a linear production process rather than a collaborative, evolving relationship.
A framework for flexible partnership in content migration
Successful migration and modernization efforts are designed to adapt. The framework we use outlines three principles for building partnership models that support both progress and quality.
1. Anchor the work in shared purpose, not fixed roles
Instead of starting with predefined responsibilities, we begin by aligning on outcomes. This creates room for flexibility while keeping everyone focused on the same goals.
Early conversations emphasize questions such as:
- What risks does outdated content pose today?
- What does “successful migration” mean for this program?
- What level of involvement feels realistic right now?
By establishing shared purpose first, teams can adjust who does the work without losing momentum or trust.
2. Separate standards from who does the work
Flexibility is only sustainable when standards are consistent. In strong partnership models, content standards are fixed, while execution is adaptable. Program offices may:
- Lead content audits using shared templates
- Draft or revise content themselves with guidance
- Collaborate on reviews while the migration team implements
Regardless of who performs the task, all content is held to the same expectations for accuracy, accessibility, clarity, and structure.
This approach allows ownership to shift without lowering quality and empowers program teams to participate in ways that make sense for them.
3. Design for shifting ownership over time
Content migration and modernization projects are rarely static. As the project progresses, capacity changes. Teams may become more confident and want to take on more responsibility or less. Flexible partnership models anticipate this by:
- Allowing engagement levels to change over time
- Providing tools, examples, and support to build confidence
- Creating clear handoffs as legacy systems are retired
Rather than locking teams into roles defined at kickoff, this approach treats ownership as something that evolves, supporting both immediate delivery and long-term sustainability.
Moving legacy content forward
Modern platforms demand more than new technology. They require new ways of working together.
When content migration and modernization efforts are approached as a partnership built on trust, flexibility, and shared standards, the process and outcomes are more resilient. Work continues even as conditions change. Ownership becomes clearer, not more fragmented. And content is better positioned to stay current long after legacy systems are gone.
Content modernization succeeds not because responsibilities are rigidly assigned, but because partnerships are designed to adapt.
