Updated September 26, 2026.
Empower Personal Dashboard lets you export transactions as a CSV from its web application. The export depends on the accounts and date range selected. A CSV is a useful record, but it is not a complete backup of every dashboard feature or proof that another app can import your history. Empower export instructions
Start by deciding what you want to preserve: a transaction archive, a spending analysis, a current account inventory or records for a future financial review. Each requires a different check.
Export the intended transactions
Empower's documented web workflow begins under Overview, then Transactions, with a CSV control next to the transaction search area. Select the relevant period and account types before exporting. The published example notes that a 90-day investment filter exports that selection rather than every historical transaction. Official CSV guide
After downloading, open the file and inspect the earliest and latest dates, included accounts and number of records. An export that opens successfully can still represent the wrong selection. Name the archive so its purpose and coverage are clear, and retain an untouched copy before editing.
Know what a transaction export cannot establish
| Record | What to verify separately |
|---|---|
| Transaction CSV | Selection, dates, accounts and actual fields included |
| Current holdings | Position details from the relevant institution |
| Cost basis | Tax-lot and acquisition records at the custodian |
| Planning assumptions | Goals and inputs you entered into planning tools |
| Original documents | Institution statements and tax records |
Do not treat a downloaded transaction list as a tax return or assume it includes every lot needed for a tax-sensitive decision. Statements and institution records remain important sources for reconciliation.
Similarly, a file of transactions does not necessarily recreate your historical net worth, budget settings or retirement scenarios. Preserve those separately where the product permits and record the assumptions you need to rebuild.
Why some history may be missing
Empower's support documentation says initial transaction retrieval depends on the financial institution. It also states that the dashboard does not currently support importing historical data from spreadsheets or other documents. Missing older history is therefore not something to fix by promising a universal CSV backfill. Historical-data limitations
If recent transactions are missing, identify the affected account and period and follow the current support process. Keep a separate archive from the institution for records outside the connected history. Label the gap so a later analysis does not mistake partial coverage for a complete period.
Choose a destination by the work you need
A spreadsheet may be enough for a private archive and a few custom calculations. A budgeting application may be useful if your priority is categories and spending reports, but confirm its specific import format and mapping rules. A portfolio-reporting tool may require transaction types, share quantities and corporate-action detail that a general spending CSV does not provide.
Mezzi is relevant when you want a connected financial picture and guidance. It should not be presented as a guaranteed importer of Empower CSV history. Current account connection and historical file migration are different capabilities.
Mezzi supports Investments, Banking, Other Assets and Liabilities, with AI Personalization for goals and preferences. Exposure X-Ray adds underlying exposure analysis for supported funds. These can help with a current financial question even while your historical archive remains elsewhere. Mezzi account groups
Test a small sample before rebuilding everything
If the destination documents an import, test a limited copy first. Compare dates, signs, account names and transfer treatment. A transfer between two of your own accounts should not accidentally become new income or spending in a household report.
For example, an illustrative $2,000 movement from checking to savings creates two records but does not add $2,000 of new household wealth. Check how the destination handles that pair before importing years of activity.
Also check duplicates. A file import and a newly connected feed may overlap. Keep a record of what you imported and the date boundaries so you can investigate discrepancies without guessing.
Reconcile the file with a small control sample
Suppose your selected month contains a $4,000 paycheck, $1,200 of card purchases and a $1,000 transfer from checking to savings. The transfer can appear as a debit in one account and a credit in another. Across your own accounts it is not another $1,000 of income or household spending.
| Control | What to inspect in the export |
|---|---|
| Paycheck | Correct account, date and $4,000 amount |
| Card purchases | The transactions making up $1,200, without also counting the card payment as new purchases |
| Internal transfer | Both sides if both accounts were selected; recognize the transfer rather than duplicate income |
| Date boundary | First and last intended transactions, including posting-date differences |
Record the selected accounts, date range, download date and row count beside the file. A count is a useful control, not a financial total. Keep the original export unchanged and make any categorization changes in a copy.
If the destination supports imports, test that copy and compare the same control transactions after import. If it only connects current accounts, evaluate the new connection separately and retain the export as an archive. Do not discard missing history because today's balance matches: a correct balance and a complete transaction record are different tests.
Preserve access until the result is verified
Do not delete the source merely because an export downloaded. Confirm that the files open, the coverage is correct and the destination meets your needs. Keep original statements independently of either application.
If you are considering a different advice workflow, run one current question through it. Verify supported accounts, add the relevant context and inspect the reasoning. There is no need to move investments simply to evaluate that conversation.
For the broader decision, see the Empower alternative checklist. A successful move leaves you with both usable records and a clearer reason for the new tool.
Frequently asked questions
Can I export Empower transactions?
Yes. Empower documents a CSV export in its web application. The selected accounts and date range determine what is exported.
Can I import missing history back into Empower?
Its current support documentation says historical spreadsheets and other documents cannot be imported. Preserve missing records separately and contact support about recent-data errors.
Can Mezzi import my Empower CSV?
Do not assume direct CSV migration. Verify destination import support separately from the ability to connect current financial accounts.
Should I delete Empower after downloading the file?
First verify coverage, readable files and the replacement workflow. Retain original institution records independently.
Start with the specific question your current dashboard leaves unresolved and verify the connected accounts behind the answer.
Start with Mezzi FreePublished by Mezzi for educational purposes. This is not personalized investment, tax, or legal advice. Prices and features were checked September 26, 2026 and can change. Comparisons use official documentation, not a matched product trial. Examples are illustrative, not customer results. Investing involves risk, including loss of principal. Account information can be incomplete or delayed. SEC registration does not imply approval or a particular level of skill.