A budget spreadsheet import should preserve what each number means before it moves anywhere. Separate account balances, recorded transactions and future plans. A spreadsheet can contain all three on one tab, but an app cannot safely treat them as the same kind of row. Make a clean copy and map one small example first.
What does each sheet actually represent?
Identify balances as of a date, events that already happened and commitments still ahead. Keep formulas distinct from stored amounts. A total cell can summarize several rows and should not also become another independent expense.
The CFPB spending and cashflow tools illustrate the different jobs of tracking and planning. Your spreadsheet's own structure determines the mapping. Do not infer a transaction merely because a cell contains a date and an amount.
Which balance is the starting point?
Choose a confirmed amount and timestamp for each relevant account. Check which historical payments it already includes. Starting from a current balance and importing earlier expenses as new future deductions can subtract the same money twice.
In a fictional sheet, checking is USD 900 after a USD 100 utility payment. The payment belongs in history. If your new plan starts from USD 900, it should not also deduct that completed USD 100 as an unpaid bill. The balance and the event remain useful, but they answer different questions.
What fields need explicit units?
Keep currency, date format, account, sign convention and purpose visible. A negative value might mean an expense, a liability or a reversal under your sheet's rules. Do not assume every negative cell is an ordinary purchase.
Use actual dates instead of ambiguous text where possible. Confirm whether 04/05 means April 5 or May 4 in the chosen locale. Preserve the original amount for foreign currency. A converted display value is not another transaction alongside the native amount.
How do you avoid duplicate records?
Give each actual event one identifiable source row. Keep an exported bank event separate from a manually entered copy of that same purchase. A total, subtotal and category summary should not all be imported as spending.
Test a small sample before a full migration. Check one income event, one expense, one internal transfer and a balance already including an earlier payment. Reconcile those cases to the source copy. Keep the untouched original file so you can understand any discrepancy without guessing what changed.
What can the current import process accept?
Use the formats and fields shown in your installed app's supported import flow. This article does not promise arbitrary spreadsheet or CSV compatibility. If a field has no supported destination, preserve it in your source record and choose a deliberate supported entry method.
Do not turn a missing mapping into an invented amount or force several meanings into one generic notes field without review. Keep private records local where possible and remove data you do not need from any file you intentionally share. Never include account passwords in an import file.
Doing this in Cashrou
Keep the paycheck planner independent from recorded Transactions. Imported activity does not automatically complete recurring Payday lines or replace a confirmed starting balance.
Use accounts and net worth for money held and the bill plan for commitments ahead. Bring a supported one-time event into Payday deliberately. A successful import is one whose meaning can be explained, not merely one that accepted every row without an error.