Project management. Smartsheet
Replacing Smartsheet with software once the grid becomes the ceiling
Smartsheet is a spreadsheet with sharing, forms, automation and dashboards on top, and that's why people like it. The grid is familiar. Nobody needs training to type in a cell. We implemented and supported it for years for PMOs and operations teams, and we were a Smartsheet partner before we canceled those partnerships to build replacements.
The grid is also the ceiling. Ask it for real structure (projects that own tasks, budgets that roll up, portfolio views, permissions by role) and Smartsheet's answer is a stack of premium capabilities plus cross-sheet formulas that one person understands. The bill grows with every person who does more than look.
Where it fits
Where does Smartsheet fit?
We implemented and supported Smartsheet for years, so this is not a hit piece. These are the cases where keeping it is the honest advice, and if yours is one of them, we will say so on the call.
A PMO or operations team whose people think in grids. They'll keep a sheet updated where they'd let a project tool go stale.
Intake and tracking. A form feeding a sheet, an approval workflow and a dashboard on top gets you a lot for very little setup.
A company standardized on Smartsheet at the enterprise level. The tool is licensed and IT has already vetted it, so the only question left is what to do inside it.
When the grid is the part people like and reporting is the problem. Custom analytics built beside Smartsheet, reading its data through the API, is often the right fix, and we'll say so when it is.
Where it breaks
Where does Smartsheet break down?
The failure modes below come from years of implementing and supporting the tool, and they are the ones that show up again and again as a company grows.
Sheets have hard limits on rows and cells. Cross-sheet references have their own. So a large program gets split across sheets and stitched back together with formulas and reports that get slower and more fragile every quarter.
Portfolio-level work needs premium capabilities licensed on top of the seat. Provisioning projects from a template, rolling status up, planning people across projects, that means Control Center, Dynamic View, Data Shuttle and Resource Management. Doing project management properly costs well above the seat.
Formulas are the business logic, and formulas break. Someone inserts a column, a linked cell moves, and a dashboard is quietly wrong until somebody notices. There's no test that catches it.
Sharing is per sheet, per report, per dashboard. Getting role-based access out of that (a client sees their project, a lead sees their team, finance sees the numbers) means duplicating sheets or adding Dynamic View. Both add maintenance.
Automation workflows cover alerts, approvals and moving rows. Then they stop. Anything with a real rule behind it, pricing or scheduling or capacity or exceptions, either lives in a formula or leaves the tool.
The end state is the one we kept walking into. Smartsheet for the grid, Excel for the analysis exported out of the grid, a second tool for the part that needed real workflow, and a renewal that grew because a few more people needed to edit.
The replacement
What does replacing Smartsheet look like?
A custom system starts from what the sheets were trying to be. Projects, tasks, budgets, resources and clients become records with relationships. The business rules become code that's tested and versioned, so they stop living in formulas one person understands. Rollups, portfolio views and role-based screens are ordinary features here, and none of them is a premium add-on.
Migration reads the sheets through Smartsheet's export and API. Each sheet gets mapped into the new structure, every formula gets read for the rule it encodes, attachments and comments come across, and cell history is kept where it matters. Then both run side by side, importing on a schedule, until the numbers match and the team stops opening the old sheets.
Some teams only need the reporting fixed. Then the same approach builds analytics beside Smartsheet and leaves the grid alone. The sheets stay the entry surface, and a custom reporting layer reads them through the API. It's a smaller project, and it keeps the door open.
You own the code, the database and the accounts. Unlimited users, no editor licensing, no premium tier standing in front of portfolio features. We're added as administrators to build and support it, and you can remove us at any time.
The stakes
What does it cost to get this wrong?
More than the software. A replacement that goes badly costs you the one thing the old system was still doing, a single place your team agrees on. The failures below each turn a rebuild into a year of parallel systems, so they are the ones we plan around.
Cell links and cross-sheet formulas don't survive an export. A linked cell comes out as the last value it displayed, so a program rebuilt from exported sheets looks right on day one and never updates again. Nobody notices until somebody quotes a number in a meeting.
Control Center blueprints, Dynamic View configurations and Data Shuttle workflows live in settings, and settings don't export. Let the premium licenses lapse before anyone documents them and that configuration is gone, along with the provisioning rules that made every project sheet look the same.
Sheets belong to individual accounts. When the person who built the portfolio rollup leaves and IT deactivates the account, the team finds out which sheets it can't administer at the worst possible moment. The rollup that fed the board pack goes with them.
The order of work
What happens, in what order, when you leave Smartsheet?
Each step exists because skipping it is how the previous attempt failed. The sequence is fixed. The runway is not, and it goes in your written scope once we know the shape of your data rather than on this page as a calendar promise.
- 01
Sheet inventory and ownership
We list every sheet, report and dashboard in the workspace with its owner, its row count and the date it was last edited. Ownership is the part that matters. Sheets belong to individual accounts, so this is where the ones tied to someone who has left turn up. We count the premium capabilities in use at the same time, Control Center and Dynamic View included.
- 02
Formulas read as rules
We read every formula for the rule it encodes, cross-sheet lookups included, since those are what hold the program together. This is where the sheets that were already wrong turn up. A column inserted years ago that shifted a reference. A rollup counting a status nobody uses now. Each rule gets written down and confirmed with whoever relies on it before we rebuild anything.
- 03
Export and history pull
Sheets export to Excel, and the API returns rows, cells, attachments, discussions and cell history. Attachments and comments need their own calls, and history comes back cell by cell, so we agree up front which columns have history worth pulling. Reports and dashboards export nothing at all. They're configuration, so we rebuild them from the questions they answered.
- 04
Build alongside the grid
The new system gets built while the sheets stay live, importing on a schedule so the comparison runs on real data and not a sample. If it turns out the grid works and only the reporting doesn't, this is where we say so, and the project becomes analytics reading Smartsheet through the API.
- 05
Reconcile, then premium licenses
Both run while the PMO checks project counts, dates, budget rollups and the portfolio view against the sheets. When those agree, the sheets go read-only for reference. Then the renewal drops the editor licenses and the premium capabilities together, and for most PMOs the premium line is the bigger of the two.
Limits
What we will not do
Saying this out loud is cheaper for both of us than finding out in month two. If one of these is what you actually want, we are the wrong firm and we will say so on the first call.
- We won't rebuild your sheets as tables. A grid of rows was the shape Smartsheet had to offer, and your program was never that shape. Copy it into a database and you get the same fragile logic with a maintenance bill attached.
- We won't promise to carry every cell of history. Some of it exports cleanly, some is expensive to pull, and some was never right to begin with. We name the columns worth keeping during scoping, so nobody finds out on cutover day.
- We won't start building while the process is still an argument. If intake works two ways depending on who picks up the request, that gets settled in discovery. Build on a disputed workflow and the system becomes the reason the dispute never gets resolved.
Questions
What people ask about leaving Smartsheet
Our whole PMO runs on Smartsheet. Can that be replaced without stopping work?
Yes, in stages. We start with whatever hurts most, usually the intake pipeline or the portfolio rollup or the resource plan, run the new system alongside it, and move the rest once the team trusts what it's seeing. Nothing switches over until the numbers have been checked against the sheets.
Can you keep our formulas?
We keep what they do. Every formula gets read for the rule it encodes, and the rules that still matter come back as tested code. The ones that only existed to work around a sheet limit get dropped. The ones that were quietly wrong get found on the way through, which is usually the part nobody expected.
We use Control Center and Dynamic View. Does a custom system cover those?
Yes, and they stop being add-ons. Provisioning a project from a template, rolling status up to a portfolio, showing each person only their slice, that's all core work in a custom build. It's scoped in from the start.
Is there a smaller option than replacing everything?
Yes. If the grid works and the reporting is what hurts, custom analytics can read your sheets through the API and give you the dashboards Smartsheet can't. Some teams stop there. Others treat it as the first step out.
What does replacing Smartsheet cost?
It depends on how many sheets and premium capabilities are in play, how many people use it, and what the new system has to connect to. So we don't publish figures. After a strategy call you get a written scope with what gets built and what it costs, measured against your current Smartsheet renewal.
What happens to our historical project data and cell history?
The rows come across in full, and history comes across where it earns the pull. Smartsheet's API exposes cell-level history, so during scoping we agree which columns matter. Usually that's approvals, status changes and anything with a money value attached. Those land as a proper audit trail with the original timestamps and the person behind each change. The rest stays readable in the archived sheets and in the raw export, which you keep. Your auditor gets a continuous trail that doesn't start at cutover.
What if we want to go back to Smartsheet?
Nothing stops you. The sheets aren't deleted at cutover. They go read-only and stay in the workspace while confidence is being built, and that's your fallback. Going back later would mean pushing from your own database into Smartsheet's API, which is ordinary work, because your data sits in a standard SQL database anyone can read. What you'd be giving up is the part that's hard to leave. Unlimited users, rules that are tested instead of typed into cells, and no premium tier standing in front of the next feature.
What about our existing integrations, like Jira or Data Shuttle?
They get rebuilt as direct connections, and most get simpler on the way. Data Shuttle exists to move files in and out of sheets because sheets can't talk to other systems on their own. A custom system talks to the source directly, so the file in the middle disappears. A Jira or accounting connector becomes an ordinary API integration with no per-connector license. And where a tool is doing genuine work, your accounting system or an e-signature provider, it stays and we integrate with it.
From the knowledge base
Guides for people weighing up Smartsheet
Reference pages, not sales pages. Each one is useful even if you decide to stay exactly where you are.
What to ask before signing a Smartsheet or monday.com renewal
The questions worth putting in writing before a work management subscription rolls over, and what a straight answer to each one sounds like.
How to tell whether your business actually needs custom software
Seven tests you can run against your own operation this week. Most businesses that run them find a configuration problem, not a build.
Related
Coming from a different tool?
The same honest treatment for the other platforms we used to implement, and the pages that explain the custom model itself.
Tell us where Smartsheet stopped fitting
Book a strategy call, or send a short note about the workarounds your team runs today. If keeping Smartsheet is the right answer, you will hear that first.