Upgrade your Investment Tracking Excel

Capitally handles the calculations that break a spreadsheet at scale — time-weighted return, money-weighted return / IRR, FX attribution between capital gain and currency gain, FIFO / LIFO / Average Cost / specific-lot cost basis, dividend and withholding-tax tracking, options Greeks — and refreshes prices automatically without formulas to maintain. See measuring investment performance for how the math compares to a spreadsheet's.

The control a spreadsheet gives you stays intact: data is yours, exportable to CSV or Excel anytime, and end-to-end encrypted on your device. CSV import and paste-from-spreadsheet are first-class flows, so migrating an existing Excel or Google Sheets tracker into Capitally is usually one paste away. See the spreadsheet-alternative feature page for the full pitch.

It replaces the need for a spreadsheet for portfolio tracking and analysis. You get more power, more automation, and more reliability, all while keeping the direct data control that made you choose spreadsheets in the first place. You can still export your data to CSV anytime.

Most migrations come in through one of three flows: paste from a spreadsheet, import a CSV / Excel export, or rebuild from broker statements. Capitally's importer maps columns to its transaction model on the fly and saves the mapping as a reusable preset variant, so a recurring source — your spreadsheet, a Kubera CSV, a Sharesight export — imports cleanly the second time.

For spreadsheet users (Excel, Google Sheets), the paste flow handles transactions, balances, and price history without changing the spreadsheet's format. For users coming from Sharesight, Snowball Analytics, Portfolio Performance, Delta, myFund or StockMarketEye - there are built-in presets. For any other tracker that exports CSV or Excel, like Kubera, Personal Capital / Empower, the same flow applies — the flexible column mapper handles whatever schema the export uses.

For broker-statement migration, native presets cover Interactive Brokers, Degiro, TastyTrade, Schwab, Coinbase, Kraken, XTB, Fidelity, Vanguard, Saxo, eToro, Trading 212, and many more; less common brokers are usually one column-mapping away. If your tracker has data Capitally doesn't yet handle directly, send a sample export to support@mycapitally.com — new presets get added regularly.

Yes. Paste transactions directly from any spreadsheet — Excel, Google Sheets, Numbers — and Capitally maps the columns into its transaction model on the fly. CSV and XLS files import the same way, with column mapping saved as a reusable preset variant, so the next paste or upload is one click. The original spreadsheet stays untouched, and your data exports back to CSV at any time.

Capitally features a robust importing interface that allows you to easily upload CSV or XLS files from any broker or app that provides transaction history or account balances. You can even copy and paste data from your own spreadsheet if you have one.

We currently support a growing list of brokers natively, including Interactive Brokers, Degiro, TastyTrade, Schwab, Coinbase, Kraken, and XTB, among others.

For individual transactions, you can simply add them manually. If you're only tracking account balances, you can update them directly in the table, along with the current market price.

While many trackers use services like Plaid or Yodlee to link to your broker automatically, these often require you to share your broker login and rarely deliver complete data. They typically only provide current balances or, at best, the last ~3 months of transactions — and almost never surface the events that move cost basis: corporate actions, dividend reinvestments (DRIP), FX conversions, deposits and withdrawals. If your broker isn't supported, which can often be the case depending on your location, you're left with manual input as most trackers don't handle bulk imports well.

Direct CSV exports go back to the day the account was opened and keep that full transaction trail intact. That's not just a privacy win — it's a precision win. With every lot, every DRIP run and every corporate action included, returns calculate correctly over the real holding period and cost basis is auditable for tax purposes. Manual entry preserves the same fidelity for assets that have no broker feed at all.

At Capitally, we prioritize your privacy and the depth of your data. That's why we're focusing on perfecting CSV imports first. Eventually, we plan to offer automated synchronization as well, so you can enjoy the best of both worlds.

Capitally supports six cost-basis methods: FIFO (first-in, first-out), LIFO (last-in, first-out), HICO (highest cost first), LOCO (lowest cost first), Manual specific-lot identification, and Average Cost Basis (ACB) with both Asset and Asset+Account pooling. You can configure the method per project, per account, per asset, or per position — the most specific setting wins. See cost basis methods for full details and worked examples.

Manual specific-lot identification is the basis for tax-loss harvesting: when you sell a partial position, Capitally lets you pick which lots to close, shows the realised gain or loss for each combination, and updates the remaining cost basis accordingly. The choice flows into the country-specific capital-gains report so the tax document reflects the actual lots you closed.

Multi-currency cost basis is preserved at the trade currency, so cross-border investors see both the local-currency realised gain (what the broker reports) and the base-currency realised gain (what their home tax authority cares about). Built-in tax presets for Canada, the UK, Germany and other jurisdictions wire the right method automatically — e.g. ACB with Section 104 same-day and 30-day matching for the UK.

Public-market positions, private investments, real estate, collectibles, fixed income, cash, and liabilities — all in the same project. Currently supported, with native pricing and dividend data:

• Stocks, ETFs, mutual funds, indexes, currencies, cryptocurrencies, commodities — see the supported markets and assets.
• Stock options on listed underlyings, with Greeks and theoretical-price modelling.
• Cash accounts in any national currency.
• Private equity (LP fund stakes with capital calls, distributions, DPI / TVPI) and managed accounts (value-based pricing).
• Real estate, startup equity, art, watches, antiques, cards, and other collectibles — priced manually or by paste / import.
• Bonds, deposits, and other fixed-income instruments — priced manually today; automated pricing is on the roadmap.
• Liabilities (mortgages, margin loans, lines of credit) for a true net-worth view.

For every asset class you choose the tracking depth: full transaction history for tax-grade reporting, or periodic balance updates when per-trade detail isn't worth the effort. See the all-investments-in-one-place overview for how it ties together.

Your financial data is end-to-end encrypted on your device with AES-GCM, using a key derived from your password — Capitally itself cannot decrypt it. We never connect to your broker or bank either: no Plaid, no Yodlee, no open-banking aggregator, no shared credentials. If our database were ever breached, the extracted data would be unreadable.

The CSV-only import path is also more accurate than aggregator sync. Broker exports usually go back to the day the account was opened and carry the corporate actions, dividend reinvestments and FX conversions that aggregators tend to drop — so cost basis stays auditable and returns reflect the real holding period.

We don't sell financial data, behavioural patterns, or any other personal information. Product analytics are limited to feature adoption and performance, are opt-out, and never include the size or value of your investments.

All servers and databases live in EU data centres, with TLS in transit, encryption at rest, and standard security practices on top of the per-user encryption. Export and permanent deletion are one-click operations inside the app — no email required.

For the full encryption model — including PBKDF2 key derivation, RSA-OAEP key wrapping, and how multi-device sync stays zero-knowledge — see the data safety guide.