PowerOpsPowerOps
Book a demo
All guides

Guide

Moving From Spreadsheets to Generator Service Software

Plan the move around equipment identity, open work, and retained history. Clean a sample first, verify the mappings, and reconcile the schedule before cutover.

By PowerOps 5 min read

Move to generator service software when it resolves a documented problem in the work. Repeated entry, ambiguous equipment names, lost service reports, and unreconciled PM schedules are useful starting points. The number of rows in the spreadsheet alone is not a reason to switch.

Keep a copy of the original files. The goal is a working schedule and traceable history in the new system, with a way to check how each record arrived there.

Find the failures in your current process

Follow a completed service job through the quote, field notes, equipment history, and invoice, noting where someone had to retype a value, select between duplicate units, or ask which file was current before they could finish the task. Check existing file permissions and version history instead of assuming a spreadsheet has no controls.

For an overdue PM, find the agreement, covered generator and ATS, promised scope, last completed visit, and person responsible for arranging the next one, then ask the vendor to demonstrate how that same work would be resolved in the replacement.

Demonstrate the replacement with the same work

Equipment identity

In PowerOps, customers, sites, equipment, and linked service records provide the context for a job. Compare the generator serial number, kW rating, fuel type, and ATS association with your source list. Imported history is useful only when it is linked to the correct equipment.

Field capture and evidence

Open the job on a technician account. Record the current readings, inspect a load bank report, and check the ATS transfer and retransfer observations. Prior visit information may be shown as reference; it must not be treated as a newly measured result.

Inspection, checklist, and service-report drafts save locally with an online session check. Reconnect to resume or submit them; they never submit in the background. Only eligible note and labor operations support automatic sync. Photos, signatures, time and status actions, and completion require a connection.

Approvals and billing

Authorized staff convert a quote into a draft work order and review its scope before approving scheduling. Winning a quote does not schedule or dispatch the job. After completion, compare the delivered work with the invoice before approving it.

Supported audited actions preserve the approving account, server timestamp, and saved snapshot in append-only records. Working forms and equipment fields can remain editable. Payment receipt can mark an invoice Paid; configured AI assistance produces drafts and does not approve workflow gates.

Prepare and test the migration

Clean a representative sample

  • Retain source identifiers so each imported record can be traced back to its original row or file.
  • Review duplicate customers, sites, and equipment before merging anything; matching names alone do not establish a match.
  • Verify missing serial numbers against source documents or the equipment. Leave unknown values marked for review.
  • Keep generator identity separate from ATS identity, and record their actual relationship.
  • Preserve load bank reports, transfer test documentation, and their original service dates.
  • Reconcile due and overdue PMs against completed visits and the signed agreement.

Agree the order and mappings

  1. Inventory the source files and agree which system owns each type of record.
  2. Establish the customer and site records needed to link equipment.
  3. Map equipment, ATS associations, covered units, and agreements against those dependencies.
  4. Review open work, quoted repairs, invoices, and the schedule before accepting the import.

PowerOps onboarding works from the data you bring. Confirm the supported import scope and column mappings; there is no promise that an arbitrary spreadsheet or another vendor's complete history will transfer without review.

CHECK THE SAMPLE

Choose records with different edge cases: multiple units at one site, an ATS linked to a generator, a missing serial, an overdue visit, and an open repair. Resolve the mapping errors before repeating the process across the full list.

Reconcile before cutover

During an agreed overlap period, name the system of record for new edits so the two copies do not drift. Compare equipment counts, covered units, due dates, and open work with the source. Find and explain mismatches before retiring the old operational file.

Retain the source archive and confirm staff can retrieve the historical documents they need. A successful row import does not prove that the attachments, permissions, schedule, or customer reports are correct.

Review the maintenance requirements

Where NFPA 110 applies, confirm the adopted edition and AHJ expectations before setting the new cadence. Check that generator, transfer switch, and load bank scope has survived the migration. Do not turn a spreadsheet date or software default into an assumed requirement.

Frequently asked questions

When should a generator service business consider moving from spreadsheets?

When staff spend too much time reconciling equipment identity, service history, due work, and billing across files. Review concrete errors and repeated entry in your current process before choosing a replacement. A spreadsheet can still be useful for analysis or an agreed export.

What should generator service software change?

Demonstrate linked customers, sites, generators, ATS records, agreements, work orders, and billing. In PowerOps, supported audited completion and approval actions preserve a named account, server timestamp, and snapshot; working forms can remain editable. Verify the actual handoffs and record scope.

How do you prepare a spreadsheet migration?

Before moving the full data set, test a sample that links equipment to the required customer and site records, maps covered units to agreements, reconciles due work against completed visits, and preserves the original service reports for later review. Agree the import order with onboarding.

Does software decide the testing cadence?

No. Confirm the governing standard, adopted edition, and AHJ requirements for the facility before configuring schedules and checklists. A template is a starting point for qualified review, not a compliance determination.

Keep reading

Run a generator service job in PowerOps.

Keep customer, site, generator, and ATS records with the work and billing. Request access for a 14-day trial that begins after approval. No card required.

Request access See the platform