Switch to PottyOps • 5 min read
Switching from spreadsheets without breaking dispatch
A safe migration starts with reviewed exports and staged import batches, not credentials, scraping, or silent AI writes into production operations.
Switching from spreadsheets without breaking dispatch
A safe migration starts with reviewed exports and staged import batches, not credentials, scraping, or silent AI writes into production operations. Most operators we work with do not want a dramatic switch. They want the spreadsheet to keep working while the new system builds a clean record in the background.
What the migration actually looks like
- Download a starter template from PottyOps for customers, jobsites, or assets.
- Copy a subset of your data into the template (one entity at a time).
- Upload the file. PottyOps detects the entity type, maps columns, and shows you a preview.
- Review the rows, fix the bad ones, and commit the clean rows to your workspace.
- Repeat for the next entity. Dispatch keeps running on the spreadsheet until the new workspace is complete.
What we deliberately do not do
- We do not ask for your spreadsheet account credentials.
- We do not silently write imported data. Every row is staged and reviewed.
- We do not invent customer records or unit records to make dashboards look pretty.
How PottyOps helps
PottyOps is built around a stage → review → commit import pipeline. The same pattern works whether you are migrating from a single spreadsheet or from an export of an old operations tool. You always see what is about to be written, and you always have the final say.
Frequently asked questions
- Can PottyOps import my existing customer and unit data?
- Yes. Upload a CSV, TSV, or Excel file and PottyOps stages it for review. Nothing is written to your workspace until you click commit.
- Will my dispatch operations be disrupted during the switch?
- No. Your existing spreadsheet can run in parallel until the import is reviewed and committed. PottyOps does not lock you in or require a hard cutover.