How Should Founders Migrate Cap Table Data After a Provider Shutdown?

What Cap Table Data Migration Actually Means

Cap table data migration is the controlled transfer of a company’s ownership records from one platform, administrator, or spreadsheet format into another system of record. The records normally include common shares, preferred shares, options, warrants, convertible securities, shareholder names and addresses, issuance dates, vesting schedules, transaction documents, tax information, and the ownership percentages calculated from those entries. Migration is not merely copying a list of investors: it requires proving that every security, right, restriction, and historical event has a valid destination in the replacement platform. A clean export is useful, but reconciliation is the work that determines whether the migration is legally and operationally dependable. For a private company, a defective cap table can affect 409A valuations, option grants, financing diligence, dividend or voting calculations, tax reporting, and the company’s ability to close a later transaction. Founders should therefore treat the destination record as a reconstruction of the company’s equity history, not as an administrative data-entry exercise. This became especially relevant after Pulley’s announced December 8 shutdown created a deadline for companies to retrieve and relocate their ownership data.

Also worth reading: What Are the Best Private Startup Cap Table Tools for Founders in 2026? · How does AI cap table management work in 2026 and what should founders actually know before switching platforms? · How Should Founders Control AI Access in a Private Deal-Flow Data Room in 2026?

Why a Provider Shutdown Creates an Urgent Migration Window

A shutdown compresses ordinary data-management work into a short period and removes access to tools that may have encoded years of company-specific decisions. By late September 2026, a company that still depends on an inactive or unsupported system should treat relocation as overdue rather than optional. The central risk is not that every entry disappears immediately; it is that records become progressively harder to retrieve, incomplete exports omit linked objects, and employees or advisers stop trusting figures that were previously generated automatically. A migration also exposes hidden dependencies, such as board approvals, signature records, option exercise documents, transfer restrictions, and stale addresses used for tax notices. These dependencies may have existed outside the cap table itself, so a provider can preserve an export without guaranteeing that the company possesses enough evidence to recreate the full record. The appropriate response is to create an evidence inventory, export early, verify checksums and row counts, and maintain both the source archive and destination backup until the transition has passed independent review. Urgency should increase the discipline around the process rather than reduce it.

A Practical Migration Process for Private Companies

The first step is to freeze unnecessary edits and appoint one accountable owner, normally a founder, finance lead, or corporate administrator working with outside counsel. The team should then export every available object, including current holdings, historical grants, cancellations, exercises, transfers, documents, and audit logs where supported. It should compare the source and destination at three levels: individual security counts, totals by class, and fully diluted ownership percentages. A small difference can represent a material governance issue; for example, one omitted option pool can change an investor’s post-money ownership by several percentage points. Board and stockholder approvals, 83(b) evidence, vesting commencement dates, and payment records should be matched to each issuance rather than accepted because the aggregate totals agree. Companies should ask qualified counsel or a cap-table specialist to review unusual instruments, side letters, repurchase rights, transfer restrictions, and any mismatch between legal ownership and spreadsheet records.

A second verification pass should recalculate ownership independently from security-level data. For a simple company, divide each outstanding security by the total number of fully diluted shares; for companies with convertible instruments, the calculation may require assumptions about conversion, exercise price, and preferred-stock conversion ratios. Those assumptions should be stored as versions rather than silently embedded in one spreadsheet. The migration file should also include a field-level dictionary explaining abbreviations, currencies, timestamps, and time zones, because an apparently identical date can otherwise change vesting or reporting treatment. Where the source system has a current cap table but incomplete historical support, the company should preserve the current snapshot while documenting every known gap. That disclosure is more defensible than fabricating historical precision or filling missing fields with guesses. Finally, the board should approve the adopted cap table if its governing documents, financing documents, or local law require formal action.

Source Exports, Cleaned Data, and Reconciliation Methods

Not all migration methods are equally reliable. A raw export preserves the provider’s original representation and is essential for evidence, but it may contain technical identifiers or inconsistent labels that users cannot readily interpret. A normalized data set is easier to import and audit because security classes, names, dates, and status fields follow a consistent structure. A manually reconstructed spreadsheet is flexible, but it introduces formula and transcription errors unless it is independently checked. The strongest process uses all three: retain the raw export, create a normalized working copy, and generate a human-readable ownership report from the verified destination. A four-column reconciliation report can classify each item as matched, corrected, unresolved, or intentionally excluded. Totals should be compared at each stage, while unresolved items should have an owner and deadline.

The reconciliation should include more than common and preferred share totals. Option counts should separate granted, exercised, cancelled, and available shares; warrants should include exercise prices, expiration dates, and remaining quantity; convertible notes should show principal, interest, discounts, caps, and conversion status. Stakeholder records should preserve legal names, tax jurisdictions where appropriate, and mailing addresses, but access to sensitive personal information should be restricted. The final archive should be encrypted, access-controlled, and stored in at least two independent locations. One copy can remain with the company and another with counsel, an administrator, or a secure data provider. The retention period should reflect corporate, tax, financing, and privacy obligations rather than a universal rule, because the applicable requirements vary by jurisdiction and company circumstances.

Comparing Cap Table Platforms and Migration Alternatives

The replacement platform should be selected for ownership modeling, document storage, audit trails, exports, permissions, and support—not only for a low headline price. Carta, Pulley’s former user community, KoreInside, and other specialist providers may fit different company sizes and workflows, and the available products and terms can change. A general-purpose spreadsheet is inexpensive and familiar, but it lacks automated reminders, role-based access, and a dependable audit trail unless carefully designed. Corporate law and accounting firms can deliver strong oversight, particularly for complex capitalization, but their services may cost more than software-only options. A spreadsheet designed for modeling can still be appropriate for a very small company with simple capitalization, provided that one person maintains it, backups are current, and counsel reviews transactions. More complex companies generally benefit from a system that records security-level history and produces controlled exports rather than relying on a single live workbook.

Pricing should be compared using total ownership cost over at least 12 months, not just the initial subscription. Relevant charges may include platform fees, implementation, data migration, per-seat access, document storage, e-signature, valuation, and support. Some providers offer a free entry tier or complimentary assistance for companies displaced by a shutdown, but that does not prove long-term suitability. Migration estimates around $1,000 to $5,000 are plausible for a straightforward company, while complex reconstruction or counsel-led work can reach $10,000 or more; these are planning ranges rather than quoted vendor prices. Founders should obtain a written scope identifying what will be migrated, which historical objects are included, who validates the result, and what support applies afterward. Data ownership and export rights should be confirmed before signing. The lowest-cost platform is expensive if it cannot preserve records or produces exports that require weeks of manual repair.

Common Migration Mistakes and Their Corrections

The most common mistake is treating a total-share count as proof that every underlying record is correct. A company can reconcile common shares to the stated total while missing an option cancellation, an expired warrant, or an unsigned stock purchase. The correction is to reconcile at the level of each security and then roll those verified entries into class totals and fully diluted percentages. Another mistake is importing only the current cap table and discarding historical grants, exercises, and supporting documents. That approach can destroy the evidence needed to explain vesting, tax treatment, and beneficial ownership, so current and historical records should be migrated whenever legally and technically available. A third error is copying percentages instead of actual quantities; percentages can become wrong after a financing, option grant, or exercise. Security quantities, terms, and conversion mechanics must remain the primary data, with ownership percentages calculated from them.

Teams also err by changing data during migration without preserving the original. Every correction should be traceable to a source document or a documented board action, and the raw provider export should remain unchanged. Importing spreadsheet-formatted numbers as text can corrupt calculations, while unrecorded timezone conversions can move a vesting commencement date by a day. Names and addresses should not be normalized in ways that obscure legal identity, and silent deduplication can merge two legitimate holders. Finally, founders sometimes wait for a perfect dataset before arranging an independent review. Perfection is unrealistic when legacy records are incomplete, so the better standard is a documented, approved reconstruction with every unresolved discrepancy disclosed.

When to Act and What to Verify Before Completion

A company should act immediately if its provider has announced a shutdown, stopped reliable exports, lost data, or discontinued support for the relevant plan. Even without a shutdown, migration should be considered when key records are held by one individual, quarterly reconciliations are skipped, or financing counsel cannot obtain a clean data room export. A useful trigger is a fixed internal deadline such as 30 days for inventory, 14 days for data transfer, 7 days for reconciliation, and 5 business days for final approval; those are project targets, not legal deadlines. The company should schedule the work before year-end administrative congestion and allow time to correct errors. A live financing, audit, 409A valuation, tax filing, or option grant should influence priority because those processes may depend on current and historical ownership data.

Completion requires more than a successful upload. The destination should show the correct authorized share count, outstanding securities, option pool treatment, class-level totals, and fully diluted ownership. The company should be able to explain every difference from the source, retain original approvals and transaction evidence, and produce a repeatable export. Counsel should confirm compliance with the company’s governing documents and applicable jurisdiction, while the finance or operations owner should confirm that payroll, tax, and investor communications use the adopted figures. Access should then be tested with separate administrator, editor, and read-only permissions. The old system should not be deleted until the board or designated officers approve the new record, backups are verified, and a recovery procedure is documented. After migration, quarterly reconciliations and annual independent reviews reduce the chance that the new platform becomes another unmanaged source of truth.

The Best Approach for Founders and Operators

The best migration is the one that leaves the company with a defensible equity record, usable historical evidence, and a clear owner—not necessarily the one performed with the newest software. For an AI private deal-flow network focused on founders and operators, reliable cap-table administration is supportive infrastructure, but it should not distract from product, customers, or responsible private deal flow. The practical sequence is to preserve the source, normalize the data, reconcile security by security, obtain appropriate professional review, and keep redundant records until confidence is established. Companies with straightforward capitalization may complete this work internally; companies with multiple entities, convertibles, side letters, or cross-border investors should involve experienced counsel or a specialist administrator. As of September 30, 2026, any company still relying on records from a provider that has shut down should treat export and validation as an active board-level data-risk project rather than a back-office chore. The target is not a prettier ownership screen; it is a source of truth that can withstand diligence, transaction, and audit questions later.