Buying field service software takes a few weeks of demos. Living with a bad rollout takes much longer. Most implementation trouble comes from data nobody cleaned, a configuration nobody owned, and training that happened once, in a conference room, a month before anyone used the app.
This guide lays out a 30/60/90-day plan for a commercial trade contractor with 10 to 50 people in the field and office. It covers the decisions to make before day one, what each phase should finish, how to prepare your data, how to train each role, and the checks to pass before moving on. We build Forz, so the last section says what our onboarding includes.
About the timeline. The 30/60/90 framing is our own planning framework: an illustrative plan, not industry data. Your rollout may be faster or slower depending on how clean your data is, how much you configure, and whether you start in your busy season. We don’t quote other vendors’ go-live timelines. Ask each vendor for a target date in writing, based on your data and your team.
Before day 1: five decisions that set the timeline
- Name one project owner. Usually the operations manager or office manager, with protected hours each week. A rollout owned by “everyone” slips.
- Decide what’s in version one. Scheduling, work orders, mobile, invoicing and accounting sync usually come first. Automations, custom reports and the customer portal can wait for the last phase.
- Inventory your data. List every source: the old system, spreadsheets, QuickBooks, paper binders, techs’ phones. Decide what moves and what gets archived.
- Pick a cutover approach. Either switch everyone on one date, or start with a pilot crew and expand. A pilot costs a little time and catches problems while they’re small.
- Check the calendar. Don’t schedule field go-live in your peak season or the week of a big inspection push.
The 30/60/90 plan at a glance
Illustrative plan, not industry data. Treat the day counts as checkpoints you can stretch or compress, not a promise.
| Phase | Goal | Main work | Exit check |
|---|---|---|---|
| Days 1–30: Foundation | The office runs today’s work in the new system | Configure job types, statuses, skills and roles; import customers, sites and active jobs; connect accounting; train office staff; start a pilot crew | Office schedules and invoices a full week without the old system |
| Days 31–60: Field rollout | Every tech works from the app | Roll out mobile to all techs; set up recurring work, service agreements and equipment records; invoice from completed jobs; set the old system to read-only | Every job for two weeks was scheduled, completed and invoiced in the new system |
| Days 61–90: Tune | The system saves time instead of just recording work | Add automations, reports and dashboards; standing routes; the customer portal; clean up leftover data | A 90-day review with a written list of what’s next |
Days 1–30: foundation
The first month is about the office. Field techs follow once the office can run a normal day without falling back on the old tools.
- Configure before you import. Set job types (inspection, repair, maintenance), the statuses your jobs move through, the skills and certifications techs hold, and user roles. Imports go more smoothly when those fields already exist.
- Import the essentials first: customers, contacts, sites and open jobs. History can follow later, or stay archived in the old system.
- Connect accounting early. Decide which system is the source of truth for customers and items, and check for duplicates before the first sync.
- Train the office on real work. Use last week’s actual jobs, not demo data.
- Start a pilot crew. Two or three techs who are comfortable with phones and willing to report problems.
Exit check for day 30: the office has scheduled, dispatched and invoiced a full week in the new system, and the pilot crew has closed real jobs from the app.
Days 31–60: field rollout
The second month moves every technician onto the app and brings recurring work across.
- Roll out mobile in waves, one crew at a time, with a pilot tech riding along or on call for questions.
- Rebuild recurring work. Maintenance visits, inspection schedules and service agreements should generate their own jobs on their cycle. Check the first full cycle by hand.
- Load equipment where it matters. If you inspect or maintain customer-owned equipment, each unit needs its own record so results attach to it.
- Invoice from completed jobs. Line items should carry from the job to the invoice. Watch for completed jobs that never got invoiced.
- Retire the old system. Set it to read-only for reference so nobody keeps a second schedule.
Exit check for day 60: for two straight weeks, every job was scheduled, completed and invoiced in the new system, and no one kept a parallel spreadsheet.
Days 61–90: tune
With the basics running, the third month is where the system starts saving time.
- Automate the handoffs your office repeats: follow-up tasks on unapproved quotes, emails when a job is scheduled, reminders before agreement renewals.
- Build three reports you’ll read weekly, for example unbilled completed jobs, open quotes by age, and jobs per tech per day.
- Save standing routes for recurring maintenance runs so they don’t get rebuilt each cycle.
- Open the customer portal for estimate approvals, reports and invoice payment once your data is clean.
- Hold a 90-day review. What’s working, what people work around, and what goes on the next 90-day list.
Data preparation checklist
Clean data is the biggest single factor you control. Start this before day 1.
| Data set | What to clean | Owner | When |
|---|---|---|---|
| Customers and contacts | Merge duplicates; separate billing contacts from on-site contacts; confirm emails | Office manager | Before the import |
| Sites and addresses | One record per service address; fix addresses that won’t map | Dispatcher | Before the import |
| Open jobs | Close or cancel stale jobs; keep only real open work | Service manager | Week before cutover |
| Equipment | Make, model, serial and location per unit, if you track equipment | Lead tech | Days 31–60 |
| Price list and items | Retire unused items; match names to your accounting system | Billing | Before connecting accounting |
| Recurring schedules and agreements | List each agreement’s visits, frequency and billing terms | Service manager | Days 31–60 |
| History | Decide what stays archived and what migrates | Owner | Before day 1 |
Training by role
Train each role on what it does every day, close to when it starts doing it in the new system.
| Role | Learn first | Format | When |
|---|---|---|---|
| Dispatchers and schedulers | Calendar, assigning and reassigning jobs, skills | Hands-on with last week’s jobs | Days 1–30 |
| CSRs and office staff | Customer and site records, creating jobs, communication | Hands-on, then shadowing | Days 1–30 |
| Billing | Job-to-invoice, accounting sync, unbilled work | Hands-on with a real week’s invoices | Days 1–30 |
| Field techs | Their schedule, job details, photos, signatures, closing a job, offline use | Short session plus a pilot tech on call | Days 31–60, crew by crew |
| Managers and owner | Reports, dashboards, approvals | Short session | Days 61–90 |
Keep one internal champion per role who knows the answers before support does.
What makes implementation timelines slip
- Dirty data. Duplicate customers and broken addresses turn a quick import into a cleanup project. Fix it before the import, not after.
- Configuring everything at once. Every custom field and automation added in month one delays go-live. Ship version one, then tune.
- No protected time. If the project owner is also dispatching full time, the project waits.
- Training too early. A session three weeks before go-live is forgotten by go-live.
- Two systems running too long. If the old schedule stays editable, people keep using it.
- Starting in peak season. Rollouts compete with your busiest weeks and lose.
Questions to ask any vendor about implementation
- What target go-live date do you commit to in writing, for our data and team size?
- Who configures the system: your team, ours, or both?
- Exactly which data does the included migration cover, and what gets quoted separately?
- How is training delivered for office staff and for field techs?
- What support do we get during cutover week, and through which channels?
- What does “onboarding complete” mean, and who signs off?
- What are the contract terms while we’re still rolling out: annual, multi-year, or month-to-month?
Where Forz fits, and where it doesn’t
Here’s what Forz includes, from our live pricing and integrations pages:
- Guided onboarding is included. Forz configures the platform for your workflows, trains your office staff and field techs, and doesn’t consider onboarding complete until you’re fully operational. There’s no extra charge (pricing).
- One standard data import is included. It covers your customers, contacts, sites and active jobs, using templates Forz provides. Larger or custom migrations, such as complex historical data or non-standard formats, can be quoted separately, and Forz tells you upfront which path fits (integrations).
- For accounting from day one, the QuickBooks Online integration connects from Settings and imports your customers, items, accounts, tax rates and payment methods. If a customer already exists in both systems, link the records before you import to avoid duplicates.
- For the field rollout, techs download the Forz mobile app for iOS or Android, sign in with their Forz credentials, and see their assigned jobs, including offline.
- Unlimited support by phone, email and chat comes with every plan. You can start month-to-month at $60 per user with no annual lock-in, or pay $50 per user per month billed annually, with a 10-user minimum.
Forz is not the right fit if:
- You need job costing or in-field mobile payments from day one. Both are on our roadmap as in progress.
- You have fewer than 10 people and don’t want to pay the 10-user minimum. New customers under 10 people with up to $1M in revenue can apply for the Small Business Program.
- You want to migrate years of complex history in week one. That’s a separately quoted migration, so scope it before you sign.
Still choosing a platform? Start with how to choose field service management software, browse our field service software roundup, or see side-by-side comparisons. To put numbers on the decision, try the FSM ROI calculator.
FAQ
How long does field service software implementation take?
It depends on your data, how much you configure, and your season. We don’t publish an industry average, and we don’t repeat other vendors’ timelines. Plan in phases, office first and then the field, and ask each vendor for a written target date. For Forz, onboarding time varies with your data and setup, and guided onboarding runs until your team is fully operational.
Should we run the old and new systems in parallel?
Briefly, if at all. A short overlap while the pilot crew tests the app is useful. After that, set the old system to read-only. When both stay editable, people keep two schedules and trust neither.