Migration
Bring the spreadsheet. Keep the week.
Export your roster from whatever you use today, drop the file in, and Weekwright works out which column is which. Nothing is created until you have seen the preview.
- Category
- Migration
- Setup
- 10 minutes for a whole team
- Who sets it up
- A manager or above
- Plans
- Every plan, including the free tier.
What you get
CSV import + Weekwright.
- Column detection that handles real competitor exports — 7shifts, When I Work, Sling, and hand-rolled spreadsheets all ship different header wording.
- A job title and an access level are told apart by their VALUES, not the header text, because exports routinely ship both a 'Role' column meaning Server and another meaning Manager.
- A preview table with the detected mapping visible before anything is written, so a wrong guess is something you see rather than something you undo.
- Idempotent: rows are deduplicated against existing members AND pending invites, so a re-import after fixing two rows does not invite everyone twice.
Setup
How it works.
- 1
Export your team from your current tool, or make a spreadsheet with name, email, and role columns.
- 2
Drag it onto the Team page. It is read in your browser — there is no upload endpoint and no storage bucket holding your staff list.
- 3
Review the preview: the detected column mapping, the rows that are ready, and the rows that need attention.
- 4
Confirm, and each ready row is sent an invite. For a rota rather than a roster, the schedule importer previews the shifts and hands them to the agent, which resolves names and positions against your org and drafts the week.
Honest limits
What this does not do.
Every integration has edges. Better you read them here than discover them the week you go live.
- The roster import invites people; it does not create shifts. Those are two different files and two different flows.
- The schedule import stops at a preview and an explicit handoff to chat rather than creating shifts directly. Turning rows into shifts needs person-to-member and position-to-position resolution plus a target week — that is a conversation, not a button, and the agent already does it well.
- It cannot invent an email address. A row with no email is flagged rather than guessed at.
- Historical data does not come across. Weekwright imports who works for you and what the week looks like, not two years of past timesheets.
Common questions
CSV import FAQ.
Can I import my team from 7shifts, When I Work, or Sling?
Yes — export your employee list from any of them and drop the CSV in. The column mapper is built against the header wording those exports actually use, including the case where the file has both a job-title column and a permission column.
What if I import the same file twice?
Nothing is duplicated. Rows are matched against existing members and pending invites, so fixing two bad rows and re-uploading the whole file re-invites only those two.
Can I import last week's schedule, not just the roster?
Yes. The schedule importer parses who works which day from when to when, previews it, and hands it to the agent to reconstruct as a draft week — which is also the fastest way to start the 'import last week, now tell me what to change' loop.
One tool for the schedule, wired into the rest of your stack.
Free for a single location, no credit card. Every plan, including the free tier.