Migration Guide

Switch from ServiceM8 to Conduit

Move from ServiceM8 to Conduit in 2026 with export planning, job-credit review, customer and invoice validation, payment setup, and rollout steps.

Switching from ServiceM8 to Conduit starts with two checks: which records your team needs for live work, and whether your ServiceM8 plan tier still matches monthly job volume. Keep ServiceM8 active until current customers, jobs, invoices, and schedules have been verified in Conduit.

See /vs/servicem8 for the comparison page and /payments for ACH and card collection details.

Verdict

Move from ServiceM8 to Conduit when team-size pricing, invoice collection savings, and a simpler contractor workflow matter more than ServiceM8’s job-credit model. Stay on ServiceM8 if unlimited users on your current tier and its mobile workflow still fit the business.

Review ServiceM8 Plan Fit

ServiceM8’s public US pricing lists plans from $0/mo to $349/mo, with paid public plans including unlimited users. The main public limiter is new jobs per month, so a switch review should include both user count and job volume.

Platform Listed monthly price Listed detail Listed 5-person team cost
ServiceM8 $0-349/mo Paid plans list unlimited users and job tiers from 50 to 1500+ new jobs/mo. $29-349/mo
Conduit $35-250/mo Every plan is built around team size. No setup costs. $65/mo

Who ServiceM8 Is Right For

ServiceM8 is right for teams that like unlimited users on paid public plans and can predict monthly job volume well enough to pick the right tier. It can also be the easier short-term choice when the field team is already trained and job-credit limits are not creating pressure.

Who Conduit Is Right For

Conduit is right for contractors that want pricing tied to team size, not monthly new-job tiers. It is especially useful when the office wants one place for customers, schedules, bids, invoices, team time, and ACH-enabled payment links.

Audit the Data You Use Daily

Do not start by moving everything. Start with the records that affect the next week of work:

  1. Active clients and site addresses.
  2. Open jobs, visits, and dispatch notes.
  3. Unpaid invoices and payment status.
  4. Quotes or estimates that may convert soon.
  5. Recurring jobs and reminders.
  6. Forms, photos, and attachments the field team checks often.

Older history can be retained in ServiceM8 during the transition if it does not need to drive daily operations in Conduit.

Export ServiceM8 Records

Review the export options available inside your ServiceM8 account before choosing a launch date. Confirm which record types can be exported directly and which items need manual review, especially attachments, forms, photos, and recurring work.

Conduit can accept CSV files or other structured records for review. Use a small export first, map fields into Conduit, and let the office compare the imported records against ServiceM8 before moving the full set.

Configure Conduit Before Cutover

Prepare the destination before inviting the whole crew:

  1. Choose the Conduit plan that matches your team size.
  2. Connect Stripe in Settings -> Payments.
  3. Add office users who will validate imports.
  4. Create tags for records that need follow-up.
  5. Decide whether any active jobs should finish in ServiceM8.

The goal is to avoid a midweek handoff where technicians do not know which system owns a job.

Validate and Launch

After the first import, compare Conduit with ServiceM8:

  • Spot-check customer names, emails, phone numbers, and site addresses.
  • Verify totals and statuses on unpaid invoices.
  • Review open jobs and scheduled times.
  • Confirm quote totals and customer links.
  • Recreate recurring jobs or reminders where needed.
  • Invite field users after office validation is complete.

Keep both systems visible for a short overlap period so the office can catch missing details without interrupting current work.

Payment Fee Savings

On a $10,000 invoice, standard card processing at 2.9% + 30 cents is about $290. Conduit’s ACH option is a $1 platform fee plus Stripe ACH processing at 0.8% capped at $5, making the ACH fee $6 on the same invoice.

This is useful to review during a ServiceM8 replacement because plan price and collection cost both affect margin. A low monthly subscription can still be expensive if larger invoices mostly run through cards.

Ready to Move Off ServiceM8?

Start with plan and job-volume review, export the current records, test a small import, then move new jobs and invoices into Conduit once the office validates the data. For the full side-by-side comparison, continue to /vs/servicem8.

FAQ

How does ServiceM8 pricing scale?

The public US pricing page lists paid plans with unlimited users and new-job limits by tier, starting at 50 new jobs/mo on Lite and rising to 1500 new jobs/mo on Premium.

What ServiceM8 data should move first?

Move active clients, site addresses, open jobs, unpaid invoices, quotes that may convert, and recurring work before older history.

Should I keep ServiceM8 during the switch?

Yes. Keep ServiceM8 available while the office compares imported records, checks invoice totals, and confirms current jobs in Conduit.

Why review payment fees during migration?

Migration is the right time to decide how customers will pay. Conduit’s ACH option can reduce fees on large invoices compared with standard card processing.

Ready to keep more of every job?

Run the work, collect faster, and keep the tools in one contractor-focused system.