What Determines the Migration Duration
The duration depends on the volume and condition of existing records, the number of business locations, custom Hedberg configurations, integrations, historical-data requirements, and the capabilities of the destination ERP. The team should also consider seasonal sales peaks, inventory counts, month-end close, and other periods when operational availability is especially important.
Before assigning dates, document the migration scope and identify dependencies between data preparation, system configuration, testing, and training. The ERP Implementation Guide for 2025 provides a broader framework for organizing ERP deployment activities, while the Businesses Cloud-Based ERP SaaS Solution System: 2026 resource can inform planning for cloud-based ERP adoption and related migration steps.
Technical architecture also affects sequencing. Reviewing How Many Levels Does a Typical ERP System Include? can help teams understand the infrastructure, application, data, and integration layers that must work together in the destination environment.
Typical Phases and Schedule
Each migration should have a schedule tailored to its scope rather than relying on a universal duration. For initial planning, a dealer might use the following illustrative eight-week schedule for a controlled migration with a defined data scope. A larger, multi-location deployment may require additional time.
- Week 1 — Discovery and scope: Confirm business requirements, source data, target fields, owners, reporting needs, and acceptance criteria.
- Week 2 — Data preparation: Review customer and vendor masters, product records, pricing, duplicates, and obsolete entries.
- Weeks 3–4 — Configuration and mapping: Configure the destination ERP, map Hedberg fields, prepare interfaces, and document conversion rules.
- Week 5 — Trial migration: Load representative records and verify data relationships, open transactions, and required attachments.
- Week 6 — Reconciliation and user testing: Compare financial balances, test daily workflows, and resolve exceptions identified by business users.
- Week 7 — Training and cutover rehearsal: Train users, confirm responsibilities, test final extraction and loading procedures, and prepare communications.
- Week 8 — Go-live and stabilization: Perform the approved final transfer, validate opening data, monitor transactions, and resolve post-launch issues.
This example is a planning baseline, not a guaranteed delivery commitment. Final dates should be confirmed after discovery, trial migration, and resource planning.
Coordinate Operational and Finance Dependencies
The timeline should account for transactions that remain active during the migration. For example, purchasing teams need to identify open requisitions and each purchase order with its ordered quantity, received quantity, remaining balance, supplier, and expected delivery date. Sales and warehouse teams must similarly agree how open customer orders, shipments, inventory transfers, and returns will be handled at cutover.
Finance needs a defined cutover date for accounts receivable, accounts payable, inventory valuation, unapplied cash, and general ledger balances. If the migration overlaps with month-end close, assign separate owners to closing activities and migration reconciliation. A Close Timeline helps clarify the sequence of period-end tasks, while an Implementation Timeline coordinates milestones, dependencies, and approvals across the broader system project.
Where supplier contracts, software subscriptions, or service agreements affect the transition, track their renewal dates, notice periods, and dependencies through a Contract Timeline. This helps the team coordinate system access and service continuity with the migration schedule.
Track Progress and Readiness
Progress should be measured by completed and approved deliverables, not simply by whether a calendar date has passed. Each phase should have an owner, planned completion date, evidence of completion, and explicit exit criteria. Maintain a central issue log that records data exceptions, responsible individuals, target resolution dates, and approval status.
Useful readiness indicators include the percentage of records successfully validated, the number of unresolved high-priority exceptions, completion of user acceptance tests, and reconciliation of financial balances. For example, if a trial migration contains 8,000 in-scope customer records and 7,840 pass the required validation checks, the validation rate is 7,840 ÷ 8,000 × 100 = 98%. The remaining 160 records should be classified and resolved or formally dispositioned before the team approves the migration.
A high validation rate indicates progress, but it does not replace checks for financial accuracy or transaction relationships. A low rate signals that additional data preparation or mapping review may be needed before the next milestone.
Best Practices for a Reliable Cutover
Assign one accountable project lead to maintain the master schedule and coordinate decisions across IT, finance, purchasing, sales, and warehouse teams. Include contingency time for correcting trial-migration findings and avoid scheduling go-live during critical business periods unless stakeholders have approved the operating plan.
Before authorizing cutover, confirm that reconciliations are signed off, users are trained, access permissions are correct, integrations have been tested, and the fallback procedure is documented. After launch, schedule daily reviews initially and track transaction processing, reporting differences, and unresolved exceptions until the new system meets agreed stability criteria.
Summary
A Hedberg Migration Timeline organizes the work required to move a furniture dealer's data and operations into a replacement ERP. Its phases typically cover discovery, data preparation, configuration, trial migration, reconciliation, training, cutover, and stabilization. Realistic dates, clear dependencies, measurable readiness criteria, and finance-team sign-off help the business coordinate the transition while protecting operational continuity and financial reporting.