# How to migrate your cap table from spreadsheet to software A step-by-step guide to auditing, cleaning, and importing your cap table data, and scaling equity without losing control. [Shannon Griffin](/content/team/shannon-griffin/index.html) Customer Success Sep 7, 2026 Last update COntributors Britt de Visser Account Executive Elin Frid Customer Success Louise Rodrigues Customer Success Table of Contents - Why founders start on spreadsheets (and why that's fine) - The five signals your spreadsheet is at its limit - What you actually gain by moving - What to gather before you migrate - What actually happens during migration - What changes on day one post-migration - Frequently Asked questions ## Why founders start on spreadsheets (and why that's fine) A spreadsheet is the correct tool for a cap table with three rows. The problem is it stays with you long after the rows multiply. ### Spreadsheets are free, flexible, and familiar. At incorporation, with two co-founders splitting equity and maybe a friends-and-family angel, a well-structured Excel or Google Sheet file handles the job. You can build a [cap table](/content/guides/cap-table/index.html) that tracks ownership, runs basic percentage math, and updates as new shares are issued. For the first year or two, that is usually enough. ### Spreadsheets are not the problem. Staying on them too long is. We see three common reasons founders do. 1. Sunk cost. you have already built the formulas, so starting over feels like a step backward. 2. Familiarity: Excel behaves the way you expect it to. 3. The "I'll migrate after the raise" trap. This quietly becomes "I'll migrate after the next raise," and so on. What we see on Cake is that the founders who arrive at onboarding are rarely bad at spreadsheets. They are usually the ones who kept theirs the cleanest for the longest. The graduation moment does not show up because the spreadsheet failed. It shows up because the next thing the founder needs to do with their cap table is something a spreadsheet cannot do. ## The five signals your spreadsheet is at its limit The tipping point is not a feeling. It is one of five specific events that make a spreadsheet structurally inadequate. Most founders who migrate hit at least two of these before they act. Here are the signals, in roughly the order they tend to appear. ### 1. You are modeling your first priced round SAFE conversion math is where spreadsheets start to break. A priced round with two or three SAFEs, a discount, a valuation cap, an MFN clause, and an option pool top-up involves a dilution waterfall that is genuinely hard to model in Excel without errors. We have seen experienced founders rebuild their spreadsheet three times in a week trying to get the pre-money and post-money numbers to reconcile. [Cap table modeling](/content/guides/cap-table-modeling/index.html) software exists because this math is not meant to be done by hand. ### 2. You have issued more than about five equity grants Vesting schedules, cliffs, exercise windows, early exercise elections, 83(b) filings. Each grant has its own timeline, and each timeline has its own tax and legal implications. In a spreadsheet, one forgotten vesting cliff or one misdated grant becomes a real problem during due diligence. Once you pass roughly five grants, manual tracking stops being a discipline problem and starts being a math problem. ### 3. An investor has asked to see an auditable cap table Due diligence is where version control chaos gets exposed. Investors do not want a PDF export of `v7_USE_THIS_ONE`. They want a cap table with a change history, a single source of truth, and role-based access. The request itself is the signal. By the time an investor asks, you usually have two to three weeks to produce something defensible, which is not a lot of time if the underlying data is scattered. ### 4. You are preparing for your first 409A valuation Valuation firms need clean source data. A spreadsheet with merged cells, three tabs named "options (old)," "options (new)," and "options (actual)," and a tab called "scratch" does not give them that. Founders often discover this the hard way, when the 409A provider asks for documentation the spreadsheet cannot produce. ### 5. You have promised employees they can "see" their equity Spreadsheets do not have access controls. You cannot share the file without sharing everything, and you cannot give an employee a view of just their own grant. The alternatives are screenshots, one-off PDFs, or a separate document for each person. Each of those creates its own version control problem. Of these five, the third is usually the one that finally pushes founders to act. The first two should have been earlier. ## What you actually gain by moving The move is not about fixing what's broken. It is about unlocking what the spreadsheet never let you do. Most founders frame migration as a cleanup project. That framing undersells it. The real upgrade is operational capability that did not exist before. ### 1. Scenario modeling in real time On Cake, you can model a $5M seed round with two SAFEs converting and a 10% option pool top-up, and watch the fully diluted cap table update as you type. You can compare three valuations side by side and see what changes at each. In a spreadsheet, that is a rebuild each time. ### 2. Auto-conversion of SAFEs and convertible notes When the priced round closes, the SAFE math runs itself. Cap, discount, MFN, pre-money, post-money are all handled. You stop being the person responsible for remembering which SAFE had which terms. ### 3. An audit trail by default Every change has a timestamp and a user. Investors and auditors expect this now. A [clean cap table](/content/guides/clean-cap-table/index.html) with a defensible history removes a category of friction from every fundraise. ### 4. Stakeholder visibility Employees see their own vesting, strike price, and what is exercisable. Investors see their holdings. You stop being the bottleneck for every "what do I own again?" email. ### 5. Compliance, integrated [409A valuations](/content/features/409a/index.html), [ASC 718 reporting](/content/feature-pages/compliance----asc-718/index.html), and [Form 3921](/content/features/form-3921/index.html) filing come out of the same platform rather than a separate vendor chain. The data does not leave the system to be re-entered somewhere else. This is what most founders mean when they say, a few weeks after migrating, that they wish they had done it sooner. They are not talking about the spreadsheet being gone. They are talking about what became possible once it was. ## What to gather before you migrate The migration itself is handled for you. The prep is what determines whether it takes two days or two weeks. When the onboarding team starts a migration, the first ask is a document pack. What we see on Cake is that founders who have these in one folder are live within a week. Founders who are hunting down a SAFE from 2023 in someone's inbox take longer. Not because migration is hard, but because reconciling incomplete source data is. Here is what to gather before you start. - **Share ledger.** Every issued share, the shareholder, the issue date, and the share class. This is the legal record your cap table is built on. For Delaware C-Corps, it is also a statutory requirement. **‍** - **SAFE and convertible note agreements.** Not just the executed copies. The full terms: cap, discount, MFN, conversion trigger, and any side letters. If you have stacked SAFEs with different terms, each one gets imported as its own instrument. **‍** - **Option grant agreements.** Grant date, vesting schedule, cliff, strike price, exercise window, and whether the grant is an ISO or NSO. Any 83(b) elections filed alongside early exercises should be filed with the grant. - **Board consents.** Signed written consents authorizing each grant, each issuance, and each share class amendment. Missing consents do not block migration, but they show up in due diligence later. **‍** - **Most recent 409A report.** If you have one. If you don't, the onboarding team can flag when you will need one. **‍** - **Incorporation documents.** Certificate of incorporation, bylaws, and any amendments to share classes or authorized shares. These define the boundaries the cap table operates inside. Once these are collected, the rest of migration is mechanical. ## What actually happens during migration Before any data moves into software, the spreadsheet needs to reconcile against your legal documents. This almost always surfaces gaps: a SAFE never added to the spreadsheet, a vesting date that does not match the grant letter, an option pool counted twice. These are not signs of a badly managed cap table. They are the natural result of tracking equity manually over time. If you are migrating yourself, those gaps are yours to find and fix. Errors in the source data carry forward into the platform. It is worth reviewing with a finance expert or lawyer before you start. Some platforms offer supported migration as part of onboarding, where their team reconciles the data against your legal documents and handles the import. Others are self-serve only, or charge extra. It is worth asking before you sign up. Either way: do not clean up the spreadsheet yourself before migrating. The instinct to tidy first is understandable, but manual edits under time pressure introduce new errors. Your signed agreements are the source of truth — not the spreadsheet. The reconciliation should work backward from those. ## What changes on day one post-migration The value shows up in the first week, when founders start doing things they could not do before. Here is what we see founders do in the first week on Cake. - **Issue a grant in minutes.** Select an employee, pick a grant template, generate a board consent, send for e-signature. What used to be a Word doc, a signature chase, and a manual spreadsheet update becomes a single workflow. **‍** - **Share investor-ready reports.** Give an investor permissioned access to their own holdings, or generate a clean fully diluted cap table as a PDF or live link. No screenshots. No cropping. **‍** - **Model the next round.** Open the modeling tool, enter a valuation and an investment amount, and see the post-money cap table. Save the scenario, share it with your co-founder, revisit it before the term sheet. **‍** - **Give employees their own view.** Each employee logs into the portal and sees their vesting, their strike price, and what is currently exercisable. The "when does my next tranche vest?" email stops arriving. **‍** - **Run a 409A.** Cake's integrated 409A valuation uses the live cap table as the source. No data export, no third-party handoff, no version mismatch between what the valuation firm has and what is on your platform today. The best measure of a successful migration is not only that the data is clean. It is what becomes possible afterward. ## Frequently Asked questions ### When should I move from a spreadsheet to cap table software? Move when you hit at least two of these: you are modeling your first priced round, you have issued more than about five equity grants, an investor has asked for an auditable cap table, you are preparing for a 409A, or you have told employees they can see their equity. Any one of these is a strong signal. Two is the tipping point most founders act on. ### How long does it take to migrate a cap table from a spreadsheet? For a seed-stage cap table with clean source documents, migration on Cake typically takes three to five business days. Cap tables with scattered or incomplete source documents take longer, usually because reconciling against missing paperwork slows the process down rather than the import itself. ### Will I lose my historical cap table data during migration? No. The import covers transaction history, not just current-state ownership, so the sequence of issuances, grants, and conversions is preserved. This matters for due diligence, 409A timing, and any future audit. ### Is cap table software worth it for a seed-stage startup? It depends on what is coming next. What we see on Cake is that seed-stage founders with fewer than 10 stakeholders, no upcoming priced round, and no equity grants tend to do fine on a spreadsheet for a while longer. Founders approaching any of the five signals above usually find the platform pays for itself in time saved and errors avoided. ### Can I migrate my cap table during a fundraise? Technically yes. In practice, we find it harder. Fundraises are the worst time to be reconciling historical data, and investor-facing work pulls founder attention away from the migration itself. Founders who migrate before a raise tend to describe the round as smoother. Founders who migrate during one tend to describe it as one more thing on fire.