How to switch budget apps in Canada (CAD export, read-only connect)

Switching budgeting apps sounds simple until you realize how much history is sitting inside the old one.

Years of transactions. Categories you've adjusted. Account balances. Recurring bills. Net-worth history. Maybe a budget you've spent months refining.

The good news is that you usually don't need to recreate everything perfectly to switch successfully.

A better approach is to treat the move like a financial handoff:

1. preserve the data you care about
2. inventory the accounts you use today
3. decide how much history you actually want
4. export before deleting anything
5. connect or create your accounts in the new app
6. import history carefully
7. fix transfers and categories
8. rebuild budgets and recurring bills
9. reconcile the new app against your real accounts

If you're moving from YNAB, Monarch, Mint, a spreadsheet or another finance app, the mechanics vary. The principles don't.

Start by deciding what you actually want to migrate

Before exporting anything, decide what you're trying to preserve.

There are two reasonable approaches.

Option 1: Preserve as much history as possible

This makes sense if you use your historical data to look at:

• spending trends
• income history
• category changes
• previous budgets
• long-term net worth
• tax or reimbursement records
• past financial decisions

If you have years of clean data and value those trends, preserving them may be worth the work.

Option 2: Keep the files, but start the new app clean

This is often easier.

Export your old data so you still own the history, but create the new financial picture using today's balances and only the recent transaction history you actually need.

You aren't losing the old information. You're simply choosing not to recreate every historical transaction inside the new system.

For someone with five years of Mint, YNAB or Monarch history, that can save a lot of cleanup.

There is no prize for successfully importing a 2019 Tim Hortons purchase that you'll never look at again.

Inventory your accounts before you migrate anything

Before creating accounts in the new app, write down what you actually have.

For a Canadian household, that might include:

Cash and banking

• chequing
• savings
• high-interest savings
• joint accounts
• USD accounts

Credit and debt

• credit cards
• lines of credit
• mortgage
• auto loans
• student loans
• other debts

Investments

• TFSA
• RRSP
• FHSA
• RESP
• LIRA
• non-registered investment accounts
• employer retirement accounts

Other assets

• property
• vehicles, if you include them in net worth
• other manually tracked assets

Record which institution holds each account and whether it is personal or shared with someone else.

If you have both CAD and USD accounts, note that too.

One important distinction: the balance inside a TFSA or RRSP can be part of your net worth; unused contribution room is not an asset.

We cover that separately in registered accounts and net worth.

Export before you cancel or delete anything

This is the most important migration rule.

Get your data out first.

Don't delete the old account because you're excited about the new app and then discover that the one thing you wanted was only available inside the account you just removed.

Save the original export somewhere you control and don't modify it.

If you need to clean or reformat the data later, make a copy and work on the copy.

Leaving YNAB: what can you export?

YNAB currently provides a fairly useful export from its web app.

According to YNAB's export documentation, you can export an entire plan by opening the plan menu and selecting Export Plan.

YNAB produces separate files containing your:

• transaction history
• categories
• category groups

Exports are provided as CSV, or TSV where appropriate for currencies that use commas differently.

There are some things the standard plan export does not preserve, including category targets and category notes.

YNAB also lets you export selected transactions if you don't want the entire history.

Don't forget YNAB's reporting history

If those reports matter to you, YNAB also supports separate exports from its Reflect section for:

• Spending Breakdown
• Spending Trends
• Income v Expense
• Net Worth

That can be useful if you're starting fresh in the next app but still want a permanent copy of what your historical YNAB data looked like.

An important YNAB migration difference

YNAB's budget is built around assigning the money you currently have to categories and priorities.

If you're moving from YNAB to a more Mint-style financial dashboard, don't expect the old plan itself to translate perfectly.

Transactions transfer more easily than budgeting philosophy.

Instead of trying to reproduce every target and category exactly, ask:

Which parts of this budget do I still want to manage in the new system?

Keep the categories that are meaningful. Drop the ones that aren't.

Leaving Monarch: preserve transactions and balance history

Monarch also gives you several ways to download your financial history.

According to Monarch's current documentation, the desktop app lets you download:

• transaction history for individual accounts
• balance history for individual accounts
• transactions across all accounts
• account balances across all accounts

Individual account transaction and balance history are downloaded as CSV files.

For all transactions, Monarch currently provides a Download Transactions option under Settings → Data.

For account-balance history, Monarch provides a CSV download from the Accounts area.

That's especially useful if preserving your historical net-worth picture matters to you.

Watch the size of large Monarch exports

Monarch currently caps individual transaction downloads at 10,000 transactions and recommends using 5,000 or fewer at a time to reduce the chance of problems.

If you have a long history, break the export into smaller pieces rather than assuming one giant file contains everything.

Monarch's documentation also says transaction and account-balance history can still be downloaded after a subscription or trial ends.

Even so, I'd export before switching. There's little reason to make an important data migration dependent on future account access.

If the old app can't export what you need

Go back to the original source.

Your budgeting app didn't create your bank transactions. Your financial institutions did.

Depending on the institution, online banking may let you download:

• CSV
• OFX
• QFX
• account statements
• investment statements
• transaction history

If an old app can't provide usable history, your bank, credit-card company or brokerage may still have it.

You can also keep older PDF statements outside the budgeting app rather than trying to convert every piece of historical information into transactions.

Don't import the entire file blindly

An export is a starting point, not a guarantee that another app will understand every column correctly.

Before importing years of transactions, inspect the file.

Look at:

• dates
• amounts
• inflows versus outflows
• account names
• merchant names
• categories
• currency
• notes or tags
• transfers

Then test with a small sample if the new platform allows it.

This is particularly important because apps can represent expenses differently. One system may export an expense as a negative number while another importer expects a different format.

A small test is much easier to undo than 20,000 incorrectly imported transactions.

Create your accounts before rebuilding the budget

The first goal should be getting the financial structure right.

That means establishing:

Accounts → balances → transactions

before spending hours creating the perfect budget.

If an account can connect automatically, connect it.

If it can't, add it manually if the new app supports manual accounts.

For something such as property, you may want a manual asset regardless.

If you're tracking a Canadian investment account, classify it properly as a TFSA, RRSP, FHSA, RESP, LIRA or non-registered account where the platform supports those account types.

Once the accounts and balances make sense, the rest of the migration gets easier.

Establish new bank connections from scratch

A bank connection isn't something you transfer from one budgeting app to another.

The new platform needs its own authorization to access financial data.

How that authorization works depends on the financial institution and the provider connecting it.

Some institutions support OAuth-style connections where you authenticate directly with the financial institution and authorize data sharing.

Other Canadian connections still rely on older aggregation methods.

Canada is in the process of implementing its formal consumer-driven banking framework, which is intended to replace screen scraping with standardized, secure API-based data sharing.

In June 2026, the federal government pre-published proposed Consumer-Driven Banking Regulations. The proposed framework is expected to come into force in stages after the final regulations are published.

That means Canadian bank connectivity is still evolving.

When connecting an account:

• understand which provider is making the connection
• pay attention to what access you're authorizing
• use OAuth or institution-hosted authorization when available
• don't weaken your bank's security settings simply to make an aggregator work
• keep multi-factor authentication enabled
• know how to revoke the connection later

And remember that “supports Canada” doesn't guarantee every Canadian institution or every account at that institution will connect equally well.

Our longer guide covers bank-sync privacy and PIPEDA considerations in Canada.

Map categories — don't recreate them blindly

Switching apps is also a good opportunity to clean up years of category clutter.

Suppose the old budget has:

• Restaurants
• Fast Food
• Coffee
• Work Lunches
• Takeout
• Date Night Dining
• Food Delivery

Maybe that detail is useful to you.

Or maybe all six categories eventually became Dining Out anyway.

You don't have to rebuild your old taxonomy simply because it exists.

Start with the categories that help you make decisions.

The Financial Consumer Agency of Canada's budgeting guidance recommends looking at actual income and expenses and distinguishing between needs and wants.

Your own system can be much more detailed than that, but categories should answer useful questions rather than create bookkeeping work for its own sake.

Be especially careful with transfers

Transfers are one of the easiest ways to break a migrated budget.

Consider three common Canadian examples.

Paying a credit card

You buy $150 of groceries on your credit card.

The $150 grocery purchase is the expense.

Later you transfer $150 from chequing to the credit card to pay the bill.

That payment shouldn't become another $150 of grocery spending.

Otherwise you've turned $150 of spending into $300.

Moving money into a TFSA

You transfer $500 from chequing into your TFSA.

Your cash moved from one asset to another.

Your net worth hasn't fallen by $500 simply because the money left chequing.

You may still want to track the contribution as part of a savings goal or registered-account planning, but it isn't the same thing as spending $500 at a retailer.

Moving money between your own accounts

A transfer from chequing to savings isn't income to the savings account and an expense from chequing.

It's your money moving between two places.

Make sure the new app recognizes transfers before relying on its spending reports.

Watch for duplicate transactions when you combine imports and bank sync

Suppose you import six months of history and then connect the same credit card.

The financial-data provider may also bring in some historical transactions.

Now the same purchase can appear twice.

This is why I prefer the following order:

1. create the account
2. establish the live connection
3. see how much history arrives automatically
4. identify the missing historical period
5. import only what is needed to fill the gap
6. review the overlap carefully

The exact behaviour varies by platform and institution, but the principle is universal:

Don't import historical transactions until you know what the live connection already brought in.

Reconcile balances before trusting reports

After your accounts and transactions are loaded, compare the new app to the source.

For every important account, check:

• current balance in the budgeting app
• current balance at the financial institution
• whether recent transactions are present
• whether pending transactions are being handled correctly
• whether liabilities have the correct sign
• whether duplicate transactions exist

For investments, also check whether the holdings shown in the new platform reasonably match the brokerage.

Don't move on to net-worth trends until today's net worth makes sense.

A beautifully rendered chart based on incorrect opening balances is still incorrect.

Rebuild the budget from your current life

This is where many migrations become unnecessarily painful.

You don't need the new budget to be an archaeological reconstruction of your old budget.

Build the budget you need now.

Start with:

• current net income
• housing
• groceries
• transportation
• utilities
• insurance
• recurring bills
• debt payments
• savings
• other meaningful spending

FCAC suggests looking at one or two months of actual spending when building a budget.

That's often enough to establish a useful starting point.

You can refine the categories after you start using the new system.

For a complete walkthrough, see how to budget in Canada in 2026.

Rebuild recurring bills separately

Imported transactions can tell the new app that Netflix charged you last month.

They don't necessarily tell it everything you want to know about the next Netflix bill.

Review recurring expenses separately:

• rent or mortgage
• utilities
• phone
• internet
• insurance
• streaming subscriptions
• software
• memberships
• loan payments
• annual renewals

Some apps detect recurring charges automatically, but it's still worth reviewing the results.

A forgotten annual renewal is exactly the kind of thing a good financial dashboard should help you see coming.

Don't forget household access

If you manage finances with a spouse or partner, decide during the migration which information belongs to:

• you
• your partner
• both of you

A joint chequing account belongs in the household picture.

Your individual TFSA may still contribute to household net worth while remaining clearly identifiable as your account.

The important part is that collaboration shouldn't require passing one login back and forth.

Look for platforms that provide separate user access and household functionality.

We cover that more deeply in household budgeting in Canada.

A practical migration checklist

Before considering the move complete, check each of these:

If those checks pass, the migration is probably in good shape.

Switching to Finnomia

Full disclosure: this guide is published by Finnomia, and Finnomia is one of the Canadian alternatives you may be considering.

Finnomia supports several ways to rebuild your financial picture rather than requiring every account to connect perfectly on day one.

You can use:

• connected financial accounts
• manual accounts
• CSV transaction imports
• manual transactions

Once the underlying data is in place, Finnomia connects it to:

• transaction categorization and custom rules
• budgeting
• recurring bills and subscriptions
• goals
• net worth
• investment holdings and transactions
• Canadian registered accounts
• debt planning
• cash-flow forecasting
• CPP/OAS-aware retirement planning
• household finances

Canadian connectivity

Finnomia currently uses Plaid for financial connections and has signed an agreement with Flinks, which is being implemented as a second connectivity provider.

The purpose of adding another provider is to improve coverage and reliability across Canadian banks, credit unions, credit cards, brokerages and investment institutions rather than depending on a single aggregation network.

Finnomia's connections are read-only. Finnomia cannot move money and does not store your banking password.

Don't feel obligated to import everything

If you're moving into Finnomia, the same advice applies:

Get today's financial picture right first.

Connect or create your active accounts.

Check the balances.

Review the recent transactions.

Fix transfers and categories.

Build the current budget.

Then decide whether older history is valuable enough to import.

Finnomia is currently completing Open Beta and exits beta on September 1, 2026. The budgeting, transaction, bill, goal, debt, investment, forecasting, retirement, net-worth and household functionality described above is already live.

You can start a 30-day free trial.

The goal isn't a perfect migration

It's tempting to judge a successful app switch by whether the new platform looks exactly like the old one.

I wouldn't.

A successful migration means you can open the new system and trust the answers to the questions that matter now:

• How much money do I have?
• What do I owe?
• Where is my money going?
• Am I staying within my budget?
• What bills are coming?
• How are my investments doing?
• What is my net worth?
• Am I making progress toward my goals?

Preserve your old data.

But don't let recreating the past stop you from building a financial system that's more useful going forward.

If you're still deciding which platform to move to, compare the best Mint alternatives for Canadians.

Product functionality and external documentation were reviewed in August 2026 and may change. Always keep an untouched copy of your original exports before importing or modifying financial data. This article provides general information, not financial advice.