Moving from a spreadsheet to scheduling software without losing a year

Most service companies don’t start with software. They start with a workbook: one tab per year, a row for each customer, columns for the months a service is due, a few notes in red. It works until the person who built it is on vacation. Moving from a spreadsheet to scheduling software is less about the new tool than about the file you already have, and the cleaner that file is, the shorter the switch.

Why the workbook stops working

A planning spreadsheet is good at one thing: showing the year at a glance. It gets weak in the places a growing company feels most:

• One person understands it. The color codes, the hidden columns and the “X means twice” rule live in someone’s head.
• It doesn’t know about the day. It says a storefront is due in March. It doesn’t say which crew, which truck, or that the drive between the first two stops takes twenty minutes.
• Nothing comes back. When the work is done, someone has to remember to mark it. History ends up in a different file, or nowhere.
• Two copies drift. The office edits one version, the owner another, and both are “the real one”.

Clean the file before you move it

Whatever system you pick, an hour of cleanup saves days of fixing imported records. Work through the file in this order:

1. One row per site and service. If a building gets exterior windows monthly and interiors three times a year, that’s two rows, not one row with a note.
2. Same customer, same spelling. “ABC Property Mgmt” and “ABC Property Management” become two customers in any system. Pick one.
3. Frequency that matches the months. A row marked quarterly with five months ticked is a question someone has to answer now, not later.
4. Hours and price per visit. If they’re missing, fill in your best estimate. They drive capacity and value reports later.
5. Addresses a map can find. Suite numbers and building names belong in their own column, not mixed into the street.

Keep the original. Clean a copy, so you can always compare.

Bring customers in first, then the work

Order matters. If your customers already live in your accounting system, import them from there first so names and billing details match what your bookkeeper sees. Then bring the recurring work over and attach it to those customers. Doing it the other way round tends to create a second copy of every customer.

In Sentra Scheduler, customers and service items come from QuickBooks Online or Desktop, with a review before anything is created. We cover the Desktop side in detail in importing customers from QuickBooks Desktop.

How the job spreadsheet import works

The job spreadsheet import reads one row per site and service: customer, address, service, zone, hours, price, frequency, week of the month and the months marked. Each row becomes a site under its customer and a recurring job with its own schedule.

Before anything is saved, it runs a dry run. Every row is parsed and checked, and the ones that don’t add up are flagged:

• a frequency that doesn’t match the months marked;
• the same site listed twice;
• no matching customer;
• a service it doesn’t recognize.

You can download the review sheet, fix the rows in your copy and upload again. When the dry run looks right, apply it. If something still looks wrong afterwards, one button undoes that whole import and nothing else.

Past visits and history

History is easy to leave behind and hard to rebuild. Past visits come over from a CSV, with your columns and values matched to your job types and statuses and a preview first. Old job numbers can stay as references, so a customer who quotes last year’s ticket number can still be found.

Imported visits show in reports and in the forecast like any other, so the first month on the new system doesn’t look like your first month in business.

What the import doesn’t do

Two things are worth knowing before you start. Imports never email customers, so nobody gets a surprise message about a visit you haven’t planned yet. And importing recurring work creates the visits that are due, but it doesn’t put them on the calendar. Scheduling them onto crews is a separate, deliberate step on the schedule.

A switchover plan that avoids a gap

1. Pick a quiet week to make the switch, not the start of your busiest month.
2. Import customers, review the matches, then import the job spreadsheet with a dry run.
3. Compare one month in the new system against the same month in the workbook. If they match, the rest usually does.
4. Schedule the first week in the new system and run it alongside the old sheet for a few days.
5. Freeze the workbook. Rename it “archive” so nobody keeps editing it out of habit.

Once the recurring work is in, the year is visible the same way the spreadsheet showed it, plus the parts it never could. For how those recurring jobs turn into visits each month, see recurring service scheduling.

The short version

Going from spreadsheet to scheduling software is mostly a data job: one row per site and service, one spelling per customer, frequencies that match their months. Clean a copy, bring customers in first, test with a dry run, and keep an undo within reach. The workbook did its job; it just shouldn’t be the only place the plan lives.