How to move finances from Excel or Finmap — to a CRM

When should you move finances from Excel or Finmap to a CRM?

It's time to move when finances and sales live in different systems and you spend hours reconciling them by hand: which clients paid, who owes, who brought in the revenue, what commission to pay.

Preparation: what to do before the first import

Preparation takes longer than the import and decides whether reports will be useful. A mess migrates in an hour and takes months to untangle.

1. Clean up your categories

Cut income and expense categories down to 20–40, grouped into 5–8 groups. Merge duplicates, delete categories unused for a year, rename vague ones ("Misc," "Other 2"). "Group → category" equals "category → subcategory" in Finmap. See the management accounting guide.

2. List every account

List every place money sits — operating accounts, business cards, currency accounts, cash registers — with currency and bank. A forgotten account shows up later as "missing" money.

3. Tidy up counterparties

One company, one spelling. "Alpha Ltd," "Alpha Limited" and "ALPHA LTD." are three different counterparties to any system. If the CRM links payments to clients by counterparty name, names in the statement and the client base must match.

4. Pick a cut-off date

The cut-off date is the day the new system becomes your book of record. The first of a month works best: the first month is complete, and its P&L can be compared with the old report. Earlier history is optional.

5. Record opening balances

On the cut-off date, record each account's bank balance and count the cash. This anchors every reconciliation. If you import from January 1, use that date's balance.

Step-by-step migration plan

This order works for any system that imports files. In brackets: how it works in 95sales CRM statement import.

1. Export your data. A bank statement per account in .xlsx or .csv, a Finmap transaction export to Excel, or your own sheet saved as .xlsx or .csv. Re-save old .xls files.
2. Check the columns. Minimum: date and amount. Ideally also counterparty, reference, category, group, project, account. Amount can be one signed column or two.
3. Map columns to fields. A good system recognizes headers on its own, but check by hand. (95sales CRM recognizes headers in English, Ukrainian, Russian and partly Polish; any column can be reassigned; bank details above the table are skipped.)
4. Run a dry run. Before anything is written, the system should show what will be imported. (The "Review" step previews the first transactions, rows to be skipped for missing date or amount, and counts of new and already-imported transactions, transfers, new accounts and categories.)
5. Import one account first. Start with the main account, check it, then do the rest.
6. Sort what wasn't recognized. (In 95sales unmatched transactions land in a queue under Transactions; your choice per counterparty is remembered.)
7. Reconcile balances for every account — formula and example below.
8. Run in parallel for a month, then compare the month's totals in both systems.

Re-uploading without duplicates

Uploading the same file twice should never create duplicates — test this in any system. In 95sales CRM each transaction gets a fingerprint built from the account, date, amount, counterparty and description, so statements with overlapping periods are safe to upload: transactions already imported are skipped.

Undoing a bad upload

A wrong upload should be rolled back as a whole, not line by line. In 95sales CRM the "Cancel" button in "Previous uploads" is available only to the owner: it removes that upload's transactions and the payments and expenses created from them, while accounts and categories stay.

How to reconcile balances after the import

Reconciling balances is the only reliable way to confirm nothing was lost. For each account, calculate the closing balance and compare it with the bank for the same date.

Closing balance = opening balance + inflows − outflows

Transfers between your own accounts must net to zero across the company: total outgoing transfers = total incoming transfers. If they don't, one side of a transfer is missing.

Worked example with hypothetical numbers

Say a service company moves off Finmap with a September 1 cut-off and runs both systems through September. All figures are illustrative.

Check for the first row: 41,200 + 68,500 − 59,850 = 49,850. The second account is $120 short. The dry run explained it: a bank fee row had no date and was skipped. Entered by hand, the difference drops to zero.

Reconciling transaction counts catches duplicates and gaps that totals can hide.

If a repeat upload shows new transactions, descriptions or amounts changed — check before building reports.

Migration checklist

Common mistakes when moving finances

1. Migrating reference lists as they are. Duplicates multiply, reports are off from day one.
2. Skipping opening balances. Without them there's nothing to reconcile against.
3. Importing every account at once. You can't tell which file broke things.
4. Skipping the dry run. Rows with no date or amount quietly disappear.
5. Forgetting transfers. A transfer between your own accounts booked as an expense understates profit. Check that transfers net to zero across the company.
6. Ignoring exchange rates. In 95sales CRM foreign-currency transactions are converted to the base currency at the rate on the upload date, not the transaction date. Upload currency statements regularly rather than a year at a time.
7. Switching off the old system right away. A parallel month is cheaper than recovering data.

What you get after moving to 95sales CRM

After the move, payments, debts and expenses live alongside clients, calls and payroll. Incoming payments link to clients by counterparty name; new counterparties can become clients on the spot. You also get a monthly P&L with category groups and projects, budget vs actual and a management balance sheet as of today. There's no transaction limit, and our team handles the transfer from Finmap.

Who should stay on Excel or Finmap

Stay put if finances aren't tied to client work or you need features a CRM lacks.

Excel or Google Sheets are enough with under a hundred transactions a month, one bookkeeper and few clients who pay predictably. More in CRM vs spreadsheets.

Finmap is the better fit if:

• you need automatic sync with banks and payment services — Finmap lists integrations with services such as Stripe, Wise and Revolut Business (per its website as of October 2026);
• expenses are entered on the go — Finmap has iOS and Android apps and a Telegram bot;
• you need a payment calendar and balance forecasts (from the Pro plan);
• your team needs one of 14 interface languages or an open API;
• you don't need a CRM, only bookkeeping: Finmap plans start at $25 a month with a 600-transaction limit.

The full comparison is on Finmap vs CRM. If your main pain is matching payments to clients, debts and payroll, moving to a CRM removes it — and the budget vs actual step by step guide covers the budgeting side.