Customer Onboarding in a Spreadsheet: When to Switch (2026)

Can you run customer onboarding in a spreadsheet?

Yes, up to a point that arrives sooner than most teams expect. A well-built Google Sheet or Excel workbook can carry customer onboarding while one person owns it, the team runs fewer than about five onboardings at the same time, and no customer ever needs to see their own status. Past any one of those three lines, the sheet stops being a source of truth and becomes a second job: someone has to remember to update it, and the moment they fall a day behind, every number in it is wrong.

You are in good company either way. OnRamp's 2026 State of Onboarding survey of 161 onboarding and customer success leaders found that only 26% are actively investing in onboarding automation, which the report reads as 74% of companies still running onboarding through some mix of spreadsheets, email threads, project management tools and recurring meetings (OnRamp, 2026 State of Onboarding). Among small and mid-sized businesses, only 13% use a purpose-built onboarding solution, and 60% of companies run onboarding across four to six separate tools (OnRamp). The spreadsheet is the default, and the default is fine right up until it starts costing you go-live dates.

This guide gives you the tracker that works while you are small, the seven signals that you have outgrown it, the real cost of staying, and the three exits (a generic project tool, a dedicated onboarding platform, or a Slack-native AI layer) with the trade-offs of each.

What should a spreadsheet onboarding tracker contain?

Two tabs, no more. A portfolio tab with one row per customer, and a plan tab with one row per task per customer. Everything else (charts, pivot summaries, the weekly numbers for your manager) is derived from those two tabs and should never be typed by hand.

The portfolio tab is the one you and your manager will actually look at. Keep it to the columns that change a decision:

The plan tab is the working checklist: customer, task, owner (you or them), due date, status, done date, notes. Build it from a template so every customer gets the same 20 to 40 tasks in the same order, then delete the ones that do not apply. If you need a starting structure for that template, use our customer onboarding plan template, and keep the customer's own deliverables visible in the same tab rather than in a separate list (our guide to tracking customer deliverables during onboarding explains why).

Three rules keep this version alive longer than most. Protect the header row and the stage dropdown so nobody adds a sixth status by accident. Add a "last updated" column that fills itself with a small Apps Script trigger, so stale rows are visible as stale. And never make a copy of the file for a customer, a manager or a quarter. The moment there are two files, one of them is wrong.

Why do onboarding spreadsheets break down?

They break for one structural reason: a spreadsheet only knows what someone typed into it, and the work of onboarding happens somewhere else. Decisions get made on calls, blockers surface in Slack, deliverables arrive by email. Every one of those events has to be noticed, remembered and re-keyed by a human before the sheet reflects reality. When the person carrying eight onboardings has a bad Tuesday, the sheet silently goes stale, and stale looks exactly like current.

That is why the visibility problem persists after a decade of tooling. In the 2026 OnRamp survey, 62% of CS leaders said they lack real-time visibility into where customers stand during onboarding, and one in three admitted they do not know where customers stand at any given time (OnRamp). Rocketlane's 2025 State of Customer Onboarding, drawn from more than 950 onboarding and implementation professionals, found 45% still struggle with information scattered across tools (Rocketlane). When Rocketlane polled practitioners specifically about spreadsheets, 35.6% said their biggest struggle was simply keeping the sheets updated and 24.4% said they could not turn the data into insight (Rocketlane poll).

The second failure is quieter. Spreadsheets are error-prone in ways their owners do not see. Ray Panko's review of decades of spreadsheet research, presented to the European Spreadsheet Risks Interest Group, reaches three conclusions: errors are rare per cell but a large spreadsheet almost certainly contains at least one wrong bottom-line value, those errors are very hard to find, and developers are highly overconfident about their spreadsheets' accuracy (Panko, arXiv). In an onboarding tracker the bottom-line value is a go-live date or a health color, and the customer usually finds the error before you do.

Hard limits matter less than people think, but they exist. Google Sheets caps a file at 10 million cells, with a beta announced in April 2026 doubling that to 20 million, and up to 100 people can edit a Sheet at once (Google Workspace Updates, Google Workspace Learning Center). Modern Excel handles 1,048,576 rows by 16,384 columns, but the legacy .xls format stops at about 65,000 rows, which is how Public Health England lost nearly 16,000 positive Covid test results in a single week in 2020 when its templates silently stopped accepting new rows (The Conversation). Your onboarding tracker will never hit a cell limit. It will hit the human limit long before that.

The 7 signals you have outgrown the spreadsheet

Any one of these is a yellow flag. Two at the same time means the switch is overdue.

1. More than five concurrent onboardings per owner. Below five, one person can hold the state of every project in their head and the sheet is a backup. Above it, the sheet is the only record, and it is the thing that gets updated last. Our guide to managing multiple onboardings at once covers the capacity math.
2. More than two people editing. Google will let 100 people in, but the second editor is the one who introduces a sixth stage name, an overwritten formula and a "v2" tab. Version drift starts at three editors, long before thirty.
3. A customer has asked "where are we?" twice in one week. The sheet has no customer-facing view, so you answer by writing a status email, which is the same information typed a third time. If you already send a weekly customer onboarding status update, count the minutes it takes to assemble.
4. Leadership wants a portfolio view or a forecast. "How many go-lives this quarter, and which are at risk?" is a saved filter in a real system and an afternoon of pivot tables in a sheet, and the answer is stale by the time the meeting starts. If you are building a customer onboarding health score in a spreadsheet, you have already hit this signal.
5. You hold a meeting to reconstruct status. If Monday's team sync exists so people can read their rows aloud and correct them, the sheet has failed at the one thing it was supposed to do.
6. Handoffs lose information. Sales to onboarding, onboarding to CSM, one owner to a backfill. If the notes column is where the history lives, the history leaves with the person. The sales to onboarding handoff is where this first shows up.
7. You need something to happen on a date without a human remembering. A reminder when a customer deliverable is three days late, a task that unlocks when the previous one closes, a health flag that recomputes overnight. Spreadsheets can approximate all of this with scripts. Nobody maintains the scripts.

What does staying on the spreadsheet actually cost?

The license is free. The labor costs real money, and the labor is what decides this. Here is an illustrative calculation; swap in your own numbers.

Take one implementation manager running eight onboardings. Keeping the tracker current takes about 20 minutes per project per week (re-keying call outcomes, chasing task status, updating dates), plus roughly two hours a week producing status updates and answering "where are we?" from customers and leadership with the sheet as the source. That is about 4.7 hours a week of pure tracker upkeep, or 12% of a 40-hour week, before any onboarding work happens. At a fully loaded cost of $60 an hour, the free spreadsheet costs roughly $280 a week, or about $14,500 a year, per implementation manager.

Compare that with the tools it would replace. Asana Starter lists at $10.99 per user per month billed annually and Advanced at $24.99 (Asana pricing); monday.com Basic starts at $9 per seat with a three-seat minimum, sold in seat buckets of 3, 5, 10 and up, with an 18% discount for annual billing (monday.com support). For a four-person team that is somewhere between $540 and $1,200 a year for a generic tool. Dedicated onboarding platforms cost more: Rocketlane's Standard plan is $49 per team member per month billed annually with a five-seat minimum, so the smallest contract is $2,940 a year (Rocketlane pricing), and our breakdown of onboarding software cost found a median observed contract of $33,044 across the category. Even at the high end, the labor spent keeping the sheet alive is the larger number for most teams under ten people.

The broader research points the same way. Asana's Anatomy of Work Index, which surveyed more than 10,000 knowledge workers, found 60% of time goes to "work about work" (chasing status, searching for information, switching between apps and communicating about work rather than doing it), and 88% said time-sensitive projects have fallen behind because of it (Asana). Microsoft's 2025 Work Trend Index telemetry shows employees interrupted every two minutes during core hours, about 275 times a day, and 48% describe their work as chaotic and fragmented (Microsoft WorkLab). A tracker that only updates when a human remembers is one more interruption competing for that attention. Teams that digitized their onboarding process in the OnRamp survey cut time-to-value by 25% or more (OnRamp), and time-to-value is what the spreadsheet is quietly costing you.

What should you move to? Three exits compared

There is no single right answer, and the wrong one is whichever tool your team will also stop updating. Match the exit to the signal that pushed you.

Two caveats. Generic project tools are the cheapest step up and most teams should take it before anything else; the trap is that they reproduce the spreadsheet's core problem, a tracker that waits for a human. Our comparison of Asana, monday.com and ClickUp for customer onboarding walks through where each one runs out. Dedicated platforms solve the customer-facing gap well, and for a professional-services org that bills time they are usually the right answer; the full landscape is in our 2026 buyer's guide to onboarding software.

Stipulate takes a different route to the same destination. Instead of asking you to move the spreadsheet into a nicer tracker, it reads the places where onboarding actually happens, the customer Slack channels and the call transcripts, and keeps the record of decisions, risks, deliverables and action items current from that. The tracker becomes a byproduct of the work rather than a task on top of it. The free plan covers one active engagement with the full manager dashboard and no per-user fees, which is a low-risk way to test whether "the sheet updates itself" holds up on a real project.

How do you migrate off the spreadsheet without losing history?

1. Freeze the sheet on a Friday. Announce a read-only date. Duplicate the file as an archive, then lock the original. No edits after this point.
2. Standardize stages before you import. Collapse the eleven statuses that have accreted into the five to seven your new tool will use. Do it in a copy of the sheet first; it is faster there than in any tool.
3. Map columns to fields, and drop half of them. Any column nobody filtered on in the last quarter stays behind. Keep the dates, owner, stage, health reason and next deliverable.
4. Import active projects only. Closed onboardings stay in the archive. Enter the 8 or 20 live ones by hand if that is faster than a CSV import; you will catch stale rows as you go.
5. Rebuild the template, then re-cut the live projects from it. Skip importing each project's task list as it stands. Apply the standard template and check off what is already done so every project has the same shape.
6. Run both for two weeks, then remove edit access to the sheet. Parallel running for longer than two weeks means the old sheet wins. The archive stays. The habit has to go.
7. Move the status update. The weekly status email now comes from the new system, or from the system watching your channels. If it still comes from the sheet, nothing moved.

Expect the whole migration to take one owner about a day for ten active projects, plus a two-hour team walkthrough. If it is taking a week, you are migrating too much history.

When should you stay on the spreadsheet?

Stay if you are under all three limits (one owner, fewer than five concurrent onboardings, no customer-facing need) and pass one more test: is the process standardized yet? Rocketlane's 2025 findings argue for identifying the patterns in your onboarding before locking in standardized workflows, and a tool freezes whatever process you bring to it. If every onboarding still looks different, the sheet's flexibility is a feature for another quarter.

Stay, too, if the budget is zero and the volume is under two new customers a month. A founder running onboarding personally with three live customers does not need a platform. What that founder does need is the two-tab tracker above, kept current, and a hard rule about when to revisit the decision: the first week two of the seven signals show up at once.

Be clear about what staying costs, though. The sheet is free; the time to keep it alive costs real money and scales in a straight line with every customer you add. Plan the exit before you need it.

Next steps

• Count your concurrent onboardings per owner and the number of people who edited the tracker last month. If either is over the line (five and two), pick an exit this quarter.
• If you are staying, rebuild the sheet to the two-tab structure above. Protect the headers, dropdown the stages, add a last-updated column, delete the copies.
• Run the cost calculation with your own numbers: minutes per project per week on upkeep, times projects, times loaded hourly cost. Put that figure next to the license price of each exit.
• If you already run customer channels in Slack, test whether the tracker can update itself: add Stipulate to one active engagement on the free plan and compare its record against your sheet after two weeks.
• Schedule the migration for a Friday freeze, and cap it at one day of work.