How to Switch Scheduling Software in a Week

Switching scheduling software feels harder than it actually is. The trick is to sequence the work right and not try to migrate the past. Here's the week-long plan that has worked for the operators we've onboarded.

Why switching feels scary

You're not just changing software. You're changing the routine your managers and staff use every week. If you do it badly, you lose a few weeks of trust and someone misses a shift. If you do it well, the team barely notices.

The key insight: you don't migrate the past, you start the future. Don't try to import historical schedules. Pick a starting week, build it fresh, and let the old tool die.

The 7-day plan

Day 1 (Monday): Set up the foundation

• Sign up. Your first month is free — up to 10 employees and 1 location, no card — which is plenty for evaluation.
• Add your locations. Drop a geofence pin on each address. Set the radius.
• Add your positions (Barista, Cashier, Server, MA, whatever your roles are).
• Set your pay period anchor (when your current period started) and length (weekly, biweekly).
• Set operating hours per location, per day of week. Coffee shop with a lunch closure? Use the split-window setting.

Total time: 30–45 minutes. Don't overthink any of these — they're all editable.

Day 2 (Tuesday): Import your team

• Export your roster from your current tool as CSV. Most tools support this — Homebase, 7shifts, When I Work, Deputy all have CSV export.
• Use Bulk CSV import — it's included for everyone. Settings → People → Import. Map columns, hit go.
• Verify pay rates and location assignments imported correctly. Touch up the few that didn't match.

Total time: 20 minutes for 30 employees. The longest part is reviewing.

Day 3 (Wednesday): Build next week's schedule

Don't migrate the past. Start with the schedule for the week starting two weeks from now. That gives you a buffer to fix anything you missed.

• Drag-and-drop your team into the next week.
• Use "Copy from last week" once you have one good week as a template.
• Set availability windows for your part-timers (they can do this themselves from their phone once invited).
• Don't publish yet. This is a draft.

Day 4 (Thursday): Invite your team

• Hit "Send invites" to your roster.
• Employees get an email + (optional) SMS to set up their account and install the PWA.
• Walk through the app with one or two trusted managers in person. They'll be your champions.
• Set up your time clock policy: GPS on/off, photo capture on/off, rounding minutes.

Day 5 (Friday): Publish + announce

• Publish the draft schedule. Employees get push notifications.
• Send an announcement: "Starting Monday, we're using PeopleBridge for the schedule. Old [tool] is read-only. Questions to [manager]."
• Keep the old tool open in read-only mode for one week as a fallback.

Days 6-7 (Saturday-Sunday): Watch and listen

The weekend is when issues surface. Mostly it's "I can't find the app on my phone" — usually a PWA install hiccup. Walk them through Add to Home Screen. Otherwise, mostly nothing happens, because the schedule is already published and visible.

Week 2: Run a full payroll cycle

The moment of truth. End of the next pay period:

• Run the timesheet report.
• Spot-check 3-5 employees against your gut sense of their hours.
• Export the CSV to QuickBooks / Gusto / ADP.
• Run payroll like normal.

If payroll comes out clean, you're done. The old tool can be cancelled.

The 4 things that actually go wrong

1. Employees don't install the app

The fix: in-person walkthrough. Two managers, one Saturday morning, 10 employees. 20 minutes total. Don't email them another link.

2. Pay rates didn't import correctly

The fix: review every pay rate before running the first payroll. CSV import gets ~95% right; you fix the rest in 5 minutes.

3. Geofence too tight or too loose

The fix: watch the first week of punches. If employees outside the building can't clock in, widen. If employees in the parking lot can clock in two stores down, tighten. See the radius guide.

4. Manager scoping wasn't set up

The fix: in Settings → People, set each manager's accessible locations. Without this, a manager at Store A can see Store B's data. Most operators forget this until it bites them.

What you don't need to migrate

• Historical schedules. They're tied to the old tool's data model. Rebuild forward.
• Historical time entries. Keep the old tool's records archived; you don't need them in the new one.
• Old announcements. They're stale anyway.
• Old messages. Start clean.

The takeaway

Switching scheduling software is a one-week project, not a one-quarter project. The biggest risk is over-planning it. Pick a Monday, follow the plan, and by Friday next week you're done.