Restoration Management Software

How to Switch Restoration Software Without Disrupting Active Jobs

In brief

Changing systems mid-season does not have to stall drying jobs, rebuilds or billing. Here is a practical cutover plan: sort your open jobs by stage, pick a migration approach, train by role, and run a short, disciplined overlap.

Most restoration companies do not switch software because they want a project. They switch because the current setup is costing them: jobs fall through the cracks, photos live on six phones, billing waits on paperwork, and nobody trusts the job board. The catch is that the work never stops while you change. There are always drying jobs on day three, rebuilds waiting on materials, and a storm forecast for next week.

This guide lays out a cutover plan that keeps active jobs moving. It assumes a small to mid-sized shop with a handful of crews, an office team of two to six people, and some mix of mitigation and reconstruction.

Why software switches go sideways

When a switch goes badly, it is rarely because the new tool cannot do the job. It is usually one of these:

  • No cutover date. People drift between the old and new systems, and nobody knows which one is the truth.
  • Migrating everything. The team spends weeks re-entering closed jobs while open ones get less attention.
  • Training everyone the same way. Technicians sit through office screens they will never touch, then do not know how to upload a photo set on site.
  • Changing the process and the tool at once without saying so. If the new system asks for a work authorization before a job can be dispatched, that is a process change. Treat it as one.
  • No owner. When the switch belongs to everyone, small decisions pile up until the project stalls.

Every step below is aimed at one of those failure points.

Step 1: Take inventory of what is actually open

Before you move anything, get an honest list of every open job and where it stands. Pull it from your current system, your whiteboard, your accounting file and your PMs' heads, because those rarely match.

Sort each job into one of these buckets:

BucketTypical stateRecommended handling
New or emergencyInspection done, equipment just setCreate in the new system right away
Active mitigationDrying in progress, daily monitoringMove into the new system with readings and photos to date
Waiting on approvalEstimate submitted, waiting on carrier or ownerMove a summary and key documents
Active reconstructionRebuild underway, subs scheduledMove into the new system with schedule and open tasks
Final billingWork complete, invoice or supplement pendingFinish in the old system
Closed with balance dueInvoiced, waiting on paymentTrack receivables in accounting, not in the migration

That last column is the key decision. You are not trying to recreate history. You are trying to make sure every job that will need daily attention over the next month lives in one place.

Step 2: Choose your cutover approach

There are three common ways to switch. None is right for every company.

ApproachHow it worksGood fit whenRisk
Hard cutoverEverything moves on one dateLow job count, slow season, strong office leadOne bad week hits every job
New jobs firstAll new losses start in the new system; old jobs finish in the old oneSteady volume, many short mitigation jobsTwo systems for weeks or months
Phased by job typeMitigation moves first, then reconstruction, or one branch at a timeMultiple divisions or locationsHandoffs between divisions get messy

For most restoration shops, a blend works best: new jobs start in the new system on a fixed date, active jobs with more than a couple of weeks remaining move over in the first week, and jobs in final billing finish where they are.

Pick the cutover date with your calendar in mind. Avoid the first week of a known storm season, the week your bookkeeper closes the quarter, and any week you are short a PM.

Step 3: Clean up before you move

Moving messy information into a new system just gives you messy information with a better interface. Spend a few hours cleaning before you import or re-enter anything.

  • Customer and contact records. Merge duplicates. Decide how you will name property managers, adjusters, TPAs and agents so they are consistent.
  • Job naming. Agree on a job number or naming convention and stick to it. Many shops use a pattern like loss type, last name and a sequence number.
  • Job types and stages. Define the stages you actually use, such as lead, inspected, authorized, mitigation, monitoring, estimate submitted, reconstruction, final, closed. Keep the list short.
  • Templates. Rebuild your standard checklists, work order templates and document templates in the new system instead of copying old ones that nobody follows.
  • Users and roles. List who needs access and at what level: owners, office staff, PMs, technicians, subcontractors and, where it fits, customers.

Step 4: Set up the new system around real workflows

Configure the system for how a job actually moves through your shop, not how a demo moves. Walk one real water loss from first call to closed file and ask, at each step, who does what and where it gets recorded.

A useful exercise is to map the handoffs:

  1. Call comes in after hours. Who takes it and where is it logged?
  2. Crew is dispatched. How do they see the address, contact and scope notes?
  3. Crew arrives. Where do the work authorization signature, first photos and initial readings go?
  4. Monitoring visits. Who records readings and equipment changes, and how does the PM see them?
  5. Mitigation complete. Who confirms equipment pickup and final readings?
  6. Reconstruction. How are subs scheduled and how do they report progress?
  7. Final. Who checks the file is complete before the invoice goes out?

Each handoff should have one place it gets recorded in the new system. If you find a step where the answer is "it depends" or "someone texts," decide the rule before you go live.

Step 5: Train by role, not by feature

Short, role-based sessions beat a single long training day.

  • Technicians and crew leads need to know how to see today's schedule, open a job, take and upload photos, add a journal note, record time and capture a signature. Thirty to forty-five minutes, on their phones, with a practice job.
  • PMs need job setup, scheduling, work orders, budgets, reviewing field documentation and customer updates.
  • Office and admin need intake, contacts, document handling, reporting and the accounting connection.
  • Owners need the reports they will look at weekly and how to find any job fast.

Train a few days before cutover, not weeks before. People forget what they do not use. Then pick one "go-to" person per crew who gets a bit of extra time and can answer the simple questions in the field.

A hypothetical walk-through: a four-crew shop in October

Picture a shop with four crews, two PMs, an office manager and a part-time bookkeeper. They have 22 open jobs: 4 brand-new water losses, 7 in active drying, 5 waiting on approvals, 3 rebuilds underway and 3 in final billing.

The operations manager owns the switch. On a Monday she builds the inventory list and assigns each job an owner. She chooses a Thursday cutover so crews have a lighter Friday to practice.

  • Monday and Tuesday: contacts are cleaned and job stages are defined. Templates for the water mitigation checklist and the rebuild work order are built.
  • Wednesday: the technicians get a 40-minute session on a practice job. The PMs get two hours. The office manager gets a half day with intake and reporting.
  • Thursday: every new call starts in the new system. The PMs move the 4 new jobs and 7 drying jobs over, each with photos and readings to date attached and a journal note saying "migrated from old system, history attached."
  • Following week: the 5 approval jobs and 3 rebuilds move over as each PM touches them. The 3 final-billing jobs stay in the old system and close there.
  • Day 21: the old system goes read-only. Anyone who needs history can look, but nobody can add to it.

Nothing about this plan is clever. It works because every job has an owner, there is one cutover date, and the overlap has an end.

Step 6: Run the overlap with simple rules

If you run two systems for a while, write the rules down and post them where everyone can see them:

  • New jobs from the cutover date forward go only in the new system.
  • A job lives in exactly one system. When it moves, the old record gets a note saying where it went.
  • Photos and readings are uploaded to whichever system holds the job, the same day.
  • The old system goes read-only on a named date.
  • Questions go to the go-to person first, then the switch owner.

Hold a 15-minute check-in every morning for the first two weeks. Ask three things: what got stuck yesterday, which jobs are in the wrong place, and what one setting or template needs fixing.

What to watch in the first 30 days

Track a few simple signals so you know whether the switch is working:

  • Same-day photo uploads. Are crews uploading before they leave the site, or batching at week's end?
  • Jobs without an owner or stage. These are your future dropped balls.
  • Time from job completion to invoice. If it gets longer, something in the closeout handoff is broken.
  • Questions repeated more than twice. Turn those into a one-page cheat sheet.
  • Workarounds. If someone keeps a side spreadsheet, find out what the system is not giving them.

Expect a dip in speed for a week or two. That is normal. What you are watching for is whether things are getting better each week.

Where RestoreUnited fits

If you are evaluating a new system, look for one that keeps the whole job in one record: scheduling and dispatch, work orders, photos and job journals, time tracking, electronic signatures and customer communication, with mobile apps for field technicians and subcontractors. RestoreUnited is built around that idea, with Job Management at the center and a QuickBooks Integration so the office is not re-keying invoices. Whatever you choose, the cutover plan above matters more than the brand.

What to do this week

  1. Name one owner for the switch and block two hours a week on their calendar.
  2. Build the open-job inventory and sort every job into a bucket.
  3. Pick a cutover date and write it on the board where everyone sees it.
  4. Define your job stages and naming convention in one page.
  5. Schedule role-based training for the three days before cutover.
  6. Set the date the old system goes read-only, and tell the team now.

See it in RestoreUnited: Job Management

RestoreUnited product video

Frequently asked questions

Should we move every open job into the new system?

Usually not. Jobs that are close to final invoice are often easier to finish where they started. Move jobs that still have weeks of work ahead, and start every new loss in the new system from a fixed date.

How long should we run both systems at the same time?

Keep the overlap as short as you can, typically a few weeks, and give it an end date before you start. The longer two systems run side by side, the more likely someone updates one and forgets the other.

Who should own the switch inside the company?

Pick one person with authority over the office workflow, often the operations manager, and give them protected time each week. Leadership should back their decisions so the change does not get renegotiated job by job.

See RestoreUnited run a restoration company

Book a live walkthrough with our team, or choose a plan and get started.