Dental records migration Gantt chart template: vendor waits and cutover

An editable Gantt chart for moving clinical records and imaging to a new dental practice system: data mapping, trial import, interfaces, parallel running, cutover on a closed day and go-live support, with vendor waits.

Use this template

What the dental records migration gantt chart template: vendor waits and cutover process is

A records migration is not finished when the data is copied. It is finished when the team can trust what they see on screen, the imaging opens and the interfaces to the lab and the payment terminal work. Most of the calendar is waiting for the vendor to build, load and correct a trial import, and a timeline helps because it shows which of your own tasks can happen during those waits and which cannot.

This template has five groups: Mapping and clean-up, Vendor build, Trial and interfaces, Parallel running and cutover, and Support. It has 22 tasks and four milestones, and a total length of 53 working days in the illustrative numbers. "Inventory records, images and interfaces" (3 working days) is the only starting task. It leads to "Map fields to the new system" (5) and "Clean duplicate and incomplete records" (6). When the mapping is done, "Send the mapping sheet to the vendor" (1) hands the clock to the vendor, and "Vendor builds the trial import" (8) runs until "Trial import ready".

The vendor wait is not idle time for you. "Clean duplicate and incomplete records" finishes before the trial import is ready, and "Set up imaging, lab and payment interfaces" (6) starts as soon as the mapping sheet is sent. Then the loop that matters begins. "Check sample records and images" (4) needs both the trial import and the cleaned records, "Report errors back to the vendor" (1) hands the clock back, and "Vendor corrects and re-imports" (5) is the second vendor wait. "Test the interfaces" (3) runs beside it, and "Mapping and trial signed off" needs both. In the illustrative numbers the interface work has about 7 working days of slack and the vendor correction does not, so the vendor sets the date.

After sign-off the plan becomes a fixed-day plan. "Train the team on the new system" (4) comes before "Run new work in both systems" (10), and "Agree the cutover day with the vendor" (1) is done once the trial is signed off. "Final extract and import on the closed day" (1) needs both the parallel run and the agreed day, so it is the natural task to give a fixed Start. "Check live records and imaging" (1) leads to "Live on the new system". After it, "Vendor support during the first weeks" (8) and "Fix issues found after go-live" (6) run side by side, and "Archive the old system read-only" (2) closes the plan at "Migration closed". All durations are illustrative: replace them with the times your vendor commits to.

A timeline schedules the work. It does not check that the migrated records are complete or that your retention and data protection obligations are met. Those differ by country, and the plan holds only the durations you give it. For related plans, see /templates/data-migration-gantt for a general migration, /templates/dental-insurance-claim-and-payment-process for the flowchart that depends on the payment interface, and /guides/gantt-chart-dependencies for how waits and joins are drawn.

What this flowchart covers

In this template

  • Five groups, Mapping and clean-up, Vendor build, Trial and interfaces, Parallel running and cutover and Support, with 22 tasks and four milestones: "Trial import ready", "Mapping and trial signed off", "Live on the new system" and "Migration closed".
  • Two vendor waits: "Vendor builds the trial import" (8 working days) and "Vendor corrects and re-imports" (5), each handed over by one of your own short tasks.
  • Your work during the waits: "Clean duplicate and incomplete records" and "Set up imaging, lab and payment interfaces" both run while the vendor builds.
  • A fixed-day cutover: "Final extract and import on the closed day" waits for "Run new work in both systems" and "Agree the cutover day with the vendor".
  • Support after go-live: "Vendor support during the first weeks" and "Fix issues found after go-live" start together, with the second linked to "Live on the new system" by a start-to-start link of 1 working day.

When to use this template

  • You are changing practice management or imaging software and need to know how long the practice will run two systems.
  • A vendor has quoted build and correction times and you want to see how late they can be before the closed day is at risk.
  • You need a cutover on a day the practice is closed and want to check it is reachable from today.
  • You manage several practices and want the same migration sequence for each.

The plan, task by task

Every task in the chart with its length in working days and what it waits for. A dependency is a step number; SS is start-to-start, FF is finish-to-finish, and +n is a lag in working days.

#TaskGroupWorking daysDepends on
1Inventory records, images and interfacesMapping and clean-up3
2Map fields to the new systemMapping and clean-up51
3Clean duplicate and incomplete recordsMapping and clean-up61
4Send the mapping sheet to the vendorVendor build12
5Vendor builds the trial importVendor build84
6Trial import readyVendor buildMilestone5
7Check sample records and imagesTrial and interfaces43, 6
8Report errors back to the vendorTrial and interfaces17
9Vendor corrects and re-importsVendor build58
10Set up imaging, lab and payment interfacesTrial and interfaces64
11Test the interfacesTrial and interfaces36, 10
12Mapping and trial signed offTrial and interfacesMilestone9, 11
13Train the team on the new systemParallel running and cutover412
14Agree the cutover day with the vendorParallel running and cutover112
15Run new work in both systemsParallel running and cutover1013
16Final extract and import on the closed dayParallel running and cutover114, 15
17Check live records and imagingParallel running and cutover116
18Live on the new systemParallel running and cutoverMilestone17
19Vendor support during the first weeksSupport818
20Fix issues found after go-liveSupport618SS+1
21Archive the old system read-onlySupport219, 20
22Migration closedSupportMilestone21

How it works

  1. Fix the dates that are real

    Give "Inventory records, images and interfaces" a fixed Start on the day you begin, and give "Final extract and import on the closed day" a fixed Start on the closed day. The plan starts on the earliest fixed Start and is scheduled forward, so a conflict flag on the cutover task shows the earliest date its dependencies allow. Compare that with the day you need.

  2. Enter the vendor's commitments

    Set "Vendor builds the trial import" and "Vendor corrects and re-imports" from the vendor's written estimates. If they quote a range, enter the longer figure and see what moves.

  3. Resize your own work

    Set "Map fields to the new system" and "Clean duplicate and incomplete records" from a sample of your own data. Check that cleaning is finished before "Trial import ready", so you are not the next wait.

  4. Length the parallel run

    Set "Run new work in both systems" to the days the team needs to feel confident. Remember that every day here is a day of double entry.

  5. Plan support

    Set "Vendor support during the first weeks" and "Fix issues found after go-live" from your contract, and decide when "Archive the old system read-only" is safe.

  6. Add owners, share and export

    Put the person responsible for each task in People, share the chart as a link with the vendor and the practice manager, and export a PDF or PNG for the project file.

Frequently asked questions

Can the chart tell me when the vendor will deliver?

No. It shows the duration you enter for "Vendor builds the trial import" and moves the dates after it. When the vendor confirms a new date, change that task and the sign-off, the training and the cutover move with it.

My cutover must be on a closed day. How do I check it fits?

Give "Inventory records, images and interfaces" a fixed Start and "Final extract and import on the closed day" a fixed Start on the day. The chart schedules forward from the earliest fixed Start. If the vendor waits and the parallel run cannot finish by then, the cutover task shows a conflict and the earliest date its dependencies allow.

Does the plan check the migrated data?

No. It schedules the work. Checking that records and images are complete is the job of "Check sample records and images" and "Check live records and imaging", which you need to staff and resize.

What if the sample check finds many errors?

Lengthen "Vendor corrects and re-imports" or add a second round of report and correction tasks. See /guides/gantt-chart-delays for reading a delay through a plan.

Can I use it for a switch of imaging software only?

Yes. Remove the tasks you do not need, keep the vendor build and the testing, and shorten the parallel run. For a general migration see /templates/data-migration-gantt.

Part of

QueryChart features for this process

Use this template

More in Operations process templates

Browse all Operations process templates