By Darryl Nash
Most conversations about ERP migration focus on go-live.
The go-live date. The readiness review. The communications plan. The support structure.
What receives far less attention—and what actually determines success—is the work that happens before it.
The preparation phase is where the real complexity lives. And in higher education, that complexity is almost always underestimated.
Data Cleanup Is the Work Nobody Wants to Do
Every institution that has migrated an ERP system eventually discovers the same reality:
Their data is not as clean as they thought.
Years—often decades—of manual entry, inconsistent usage, and undocumented processes create data environments that break under the pressure of migration.
Common issues include:
- Duplicate student records across departments
- Financial aid data that doesn’t reconcile with finance records
- Outdated or retired academic programs still active in the system
- HR data inconsistencies that block automation
- Invalid or incomplete identity and address data
Data cleanup is not glamorous. It requires time, coordination, and institutional commitment.
When institutions delay cleanup until after go-live, they’re choosing to go live with known problems—and pay more to fix them later.
Process Redesign Must Happen Before Configuration
One of the biggest mistakes institutions make is configuring the new system to behave like the old one.
It feels safe. It reduces resistance.
But it eliminates the value of the migration.
ERP systems are designed with different logic, workflows, and capabilities. Forcing a new system to replicate old processes carries forward inefficiencies instead of eliminating them.
Effective pre-implementation work includes:
- Documenting current workflows to understand purpose—not replicate steps
- Identifying which processes are policy-driven vs. system-driven
- Designing workflows based on the new system’s capabilities
- Aligning leadership on process decisions before configuration begins
This is transformation work—not technical work.
Cross-Department Collaboration Is Not Optional
ERP systems don’t belong to one department.
They span the entire institution:
- Financial Aid
- Registration
- Student Accounts
- Human Resources
- Finance
- Academic Affairs
When departments plan in isolation, integration issues surface late—often during testing or go-live.
Typical breakdowns include:
- Financial aid structures that don’t align with finance
- Term structures that conflict with academic planning
- Data dependencies that weren’t identified early
Cross-functional collaboration during pre-implementation ensures these issues are identified early—when they are easier and less costly to fix.
Governance Planning Before Go-Live Determines Stability After
Governance does not begin at go-live. It should already be in place.
Institutions that fail to define governance early struggle during stabilization.
Pre-go-live governance planning should define:
- Who approves system changes after go-live
- How support requests are prioritized
- Escalation paths for cross-department conflicts
- Transition from implementation team to operational support
Without this structure, post-go-live becomes reactive instead of controlled.
The Work Before Go-Live Determines Everything After
The preparation phase rarely gets attention in executive dashboards.
There are no milestone celebrations for data cleanup.
No announcements for process redesign.
No recognition for governance planning.
But this is the work that determines whether go-live is smooth—or chaotic.
A Leadership Question Worth Asking
If your ERP went live tomorrow, how confident are you that your institution’s data and processes are truly ready?
That confidence is not built at go-live.
It is built in the work that happens before it.
