How to migrate your cap table from Carta to Glide Equity

Before you export anything from Carta

Carta says company reports are regenerated from near-real-time cap-table activity. Treat the five files as one coordinated snapshot: finish pending corrections first, choose a single as-of date, and generate the whole bundle in one session. If someone issues, cancels, exercises, or edits a security between exports, the reports may describe different states and Glide will stop the migration.

• Confirm you selected the correct company in Carta, especially if your login administers multiple entities.
• Use an administrator or other role that can access Essentials and Run Reports.
• Choose the current date unless you intentionally need a historical opening snapshot.
• Leave draft securities out of the cap-table export. Migrate finalized records, then recreate or issue unfinished drafts in Glide after the workspace is ready.
• Create a new local folder for the five downloads so older exports cannot be selected accidentally.
• Confirm each original XLSX file is no larger than 10 MB. If a legitimate export exceeds that limit, contact Glide instead of splitting or modifying it.

The five Excel files Glide requires

Export the reports from Carta

Carta notes that some accounts use “shares” where others use “certificates.” That wording difference does not change the Glide process. What matters is selecting the five named reports and preserving their workbook structure.

Upload the five files to Glide Equity

What Glide checks before it creates the workspace

• Exactly five XLSX workbooks are present, one for each required report type.
• Every workbook belongs to the same company and uses the same as-of date.
• Required worksheets, columns, and authoritative numeric cells are present.
• Stakeholder IDs, names, and security-holder relationships agree across reports.
• Issued, outstanding, forfeited, vested, unvested, exercised, expired, cancelled, converted, and repurchased quantities remain internally valid.
• Share-class totals, equity-plan reserves, award balances, and fully diluted capitalization reconcile across the cap table, ledger, and OCX views.
• Prices and cash values retain the exact decimal values written into the XLSX files rather than being rounded through ordinary spreadsheet-number conversion.
• Source files stay within safe compressed, expanded, worksheet, row, and cell limits.

This strictness is intentional. A cap-table migration should not “mostly import” and leave an administrator to discover missing shares later. Glide either proves the bundle agrees and commits the workspace atomically, or leaves the organization unchanged and explains what failed.

Review legal terms after the migration

Cap-table reports prove balances and relationships, but they are not a substitute for the charter, board approvals, equity-plan documents, grant agreements, or legal advice. Some governing terms are not authoritative fields in the five reporting workbooks. Glide highlights those terms for confirmation instead of inventing legal facts.

• Compare each share class against the charter: authorized amount, par value, voting rights, and conversion ratio.
• Compare each equity plan against its approved plan document and board consents: reserve, underlying class, and cancellation or return-to-pool behavior.
• Review any imported Carta Data Warnings and resolve the underlying record or formally acknowledge the issue.
• Spot-check the largest stakeholders and every unusual security before recording new transactions.
• Keep independent copies of governing documents and the original five exports according to your company’s retention policy.

Invite stakeholders after verification

Once the workspace is ready, an Equity admin can open Stakeholders and send email invitations. Each recipient accepts through a private, single-purpose link. Acceptance gives that person access to their own linked securities and documents; it does not grant access to the company-wide cap table or Glide’s bills, approvals, payroll, and other organization products.

1. Review stakeholder names and email addresses before sending.
2. Select the stakeholders who should receive access and send invitations.
3. Ask each recipient to accept using the same email address associated with the invitation.
4. Use the Team and Stakeholders views to monitor pending, accepted, revoked, and resend states.
5. Confirm a sample holder sees only My equity, My securities, My documents, and Updates.

Troubleshooting common migration errors

Migration checklist

• Correct company selected in Carta
• Carta health checks reviewed
• One as-of date used everywhere
• Summary/Intermediate/Detailed cap table downloaded as XLSX
• Stakeholder Details downloaded as XLSX
• All Stakeholders Ledger downloaded as XLSX
• Securities Ledger downloaded as XLSX
• OCX downloaded as XLSX
• Original filenames and workbook contents preserved
• All five files show ready in Glide
• Verification completes without a reconciliation error
• Share-class and plan legal terms confirmed against governing documents
• Stakeholder emails reviewed before invitations are sent