Most founders coming to Octelligence are not starting from zero. They have a cap table in Carta or an Excel sheet, a minute book in a Google Drive folder, and a stack of signed share certificates in a desk drawer. This guide walks through the migration path for each common starting point and how to reconcile the result before you cut over.
The general migration shape
Regardless of where you're coming from, every Octelligence migration follows the same arc:
- Snapshot: capture the source system at a fixed point in time so the migration target is stable
- Map share classes: set up the classes in Octelligence before importing holdings
- Import holders: add every shareholder, option holder, and warrant holder
- Record historical issuances and transfers: recreate the chain of title with original dates
- Import outstanding options and warrants: including vesting schedules
- Reconcile: totals in Octelligence should match totals in the source system exactly
- Cut over: make Octelligence the system of record and freeze the source
Migration is self-serve on every plan. CSV import covers corporations, people, share classes, option grants, warrants, restricted stock and SAFEs; record historical issuances and transfers with their original dates.
From Carta
Carta exports a "Cap Table Export" CSV that contains shareholders, share classes, and outstanding holdings, plus separate exports for stakeholders and option grants. For a Carta migration, the recommended path is:
Pull the Carta export
In Carta, go to Cap Table › Export and download the all-securities CSV. Also export the stakeholders CSV, the option grants CSV, and anything in Carta › Documents (incorporation documents, resolutions, board approvals).
Import the exports
Map Carta's columns to the Octelligence CSV import for people, share classes, option grants, warrants and SAFEs. Then record historical issuances and transfers with their original dates, and reconcile the totals against the Carta export before cutover.
Build the minute book in parallel
Carta doesn't keep a structured minute book, so this side of the migration is greenfield. Upload the resolutions and authorizing documents you exported from Carta and turn them into minute book entries with effective dates and resolution types. If you have additional minute book material elsewhere (Google Drive, counsel's files), include it.
From Pulley
Pulley's exports are similar to Carta's (security holders, share classes, option grants), so the field mapping follows the same pattern. Pulley does not maintain a minute book, so the corporate records side starts fresh; if counsel has been keeping a minute book in a separate location, this is the moment to bring it together with the rest of the migration package.
Import your Pulley exports the same way, and gather any minute book material you want included.
Pulley has announced that it will cease operations and services on December 8, 2026 (see Pulley's shutdown FAQ), so the usual advice below about keeping the source system live until reconciliation is clean has a hard end date. Download your cap table workbook and documents first, and reconcile against those saved files. For an overview of moving from Pulley, see Migrate from Pulley.
From Mantle
Mantle handles Canadian entities natively, so jurisdictional fields, ISC register entries, and share class structures usually map cleanly to Octelligence. Mantle's exports cover cap table, option grants, and corporate records.
Import your Mantle exports using the CSV import. The minute book and filings calendar are where the migration adds the most value. Mantle covers some of this, Octelligence covers it more completely.
From Cake Equity
Cake's export covers cap table, ESOP grants, and SAFE/convertible holdings. Cake is strongest on options, so option grants with vesting schedules are usually the cleanest part of the import.
Cake users moving to Octelligence are typically motivated by the need for verifiable share certificates and a proper corporate records layer. Neither is part of Cake's depth. Plan the migration to include both: import the Cake exports and upload any minute book material you have.
From Excel or Google Sheets
If your cap table lives in a spreadsheet, the migration is straightforward but requires more cleanup than a vendor export. Before you start, make sure each issuance row has:
- Holder name, email, jurisdiction
- Share class
- Number of shares
- Issuance date
- Consideration amount and type
- Original certificate number, if any
Use the CSV import for people and share classes (and for option grants, warrants, restricted stock and SAFEs where you have them), then record each issuance with its original date and reconcile against your existing share register. Expect to spend an hour or two cleaning up holder names and consideration entries that are inconsistent in the source sheet. That cleanup pays back at every diligence afterward.
From paper records
If your minute book is a binder and your cap table lives in your head, you're not unusual, and the migration is more about discipline than data wrangling.
Set up the corporation in Octelligence
Run through the Getting Started flow as if you were brand new.
Scan and upload constitutive documents
Articles of incorporation, bylaws, unanimous shareholder agreement, any articles of amendment. Upload to Records › Constitutive documents in chronological order.
Enter share classes
Based on the articles of incorporation, set up each class with the same authorized counts and rights as the original.
Recreate historical issuances
For every signed share certificate in the binder, enter a corresponding issuance in Octelligence with the original date and original certificate number. Octelligence will generate new QR-verified certificates that supersede the paper ones for verification purposes, but the original date and number are preserved.
Recreate historical transfers
Walk through each transfer agreement in chronological order, recording transfers as historical events. Octelligence preserves the chain of title even when entered retroactively.
Scan and structure minute book entries
For each resolution and meeting in the paper binder, create a structured entry in Records › Minute book and attach the signed scan. Resolutions for issuances should link to the corresponding cap table entry.
This is the most time-intensive migration path. Work through the records one year at a time and reconcile as you go.
Reconciliation checklist
Before cutting over from the source system, verify:
- Total issued shares per class in Octelligence matches the source system
- Fully-diluted ownership totals match (within rounding)
- Every holder in the source system exists in Octelligence with matching share counts
- Every outstanding option grant has matching strike price, vesting schedule, and unvested balance
- Every SAFE or convertible has matching principal, cap, discount, and MFN provisions
Reconciliation reports are available under Cap Table › Reports › Reconciliation. The first run after import shows any deltas.
Cutover
Once reconciliation is clean:
- Notify holders that Octelligence is now the system of record
- Update outstanding agreements that reference the old platform
- Mark the source system as read-only or export-only
- Cancel the source subscription on its next renewal date (not immediately, keep it available for any reconciliation checks)
- Issue fresh QR-verified certificates to existing holders (optional but common; the old certificates remain valid)
Questions during migration. Email support@octelligence.com. Every plan includes email support, with priority email support on Scale and Intelligence.
Common gotchas
Importing without first setting up share classes. The import fails or misclassifies holdings if the share classes don't already exist in Octelligence with the same names. Always set up share classes first.
Skipping historical transfers. If you only import the current state, the chain of title gap will surface at the next diligence. Take the time to record historical transfers, even old ones.
Cancelling the old subscription before reconciliation. Keep the source system live until the reconciliation report is clean and you've issued any replacement certificates. Cancel on the next renewal, not before.
Migrating without counsel's awareness. If you have outside counsel, loop them in before cutover. They may have a parallel record they want reconciled, and they'll be the ones using Octelligence at the next financing.