Moving from Copilot Money
On this page
If you've been tracking your money in Copilot Money, you can bring your transaction history into Pennyweight. You export a CSV from Copilot, and your AI reads it and sends the rows to Pennyweight, one account at a time. New to importing? Start with how importing works.
Export from Copilot
These steps are per Copilot's help center, and its menus can change.
- On iPhone. Open Settings, scroll to Account, and tap Export your transactions. Copilot opens a CSV file of your transactions. Use the share button in the lower left corner to save it to Files or send it on.
- On iPad or Mac. In the Transactions tab, apply filters or search for a merchant or transaction name, then export the transactions that match.
- On the web. In the Transactions tab, use the web app's filters to choose the transactions to export.
Per Copilot, the export includes the date, name, amount, pending or posted status, category and parent category, whether the row is excluded, the transaction type, the account and account mask, notes, and associated recurrings.
How to do it
- Share the CSV with your AI.
- Tell it which Pennyweight account each Copilot account goes into. The file names an account on every row, so your AI splits it and imports one batch per account.
- Decide on pending and excluded rows. A pending row can still change, so ask your AI to leave it out and bring it in once it posts. An excluded row is different: per Copilot, excluding only keeps a transaction out of Copilot's spending totals. The money still moved, so ask your AI to list excluded rows and keep them unless you say otherwise.
- Check the signs. Pennyweight stores money out as negative and money in as positive. If your file shows spending as positive numbers, tell your AI so it flips them.
- Use the category column for categories. The transaction type column says whether a row is regular spending, income or an internal transfer, which isn't a category.
- If an account doesn't exist in Pennyweight yet, ask your AI to add it. A new manual account needs an opening balance before its first import: the balance just before the first row. For a credit card, give what you owed as a positive number. See add a manual account.
- Your AI shows a preview for each account: new rows, likely duplicates and rows that need a look. Nothing is saved yet. Check that the balance moves the way you expect. See reading an import preview.
- Say yes to import, then work through after you import.
copilot.csv is my Copilot Money export. Spending is a positive number in this file. Leave out any pending rows, and list any excluded rows before importing them. Import only the Everyday Checking rows into my Everyday Checking account, using the category column as the category, not the type column. Show me the preview, then ask me once before saving.
Before I import copilot.csv, tell me how many rows are pending, how many are marked excluded, and how many rows each account has. Don't import anything yet.
What you'll see
For the first prompt, your AI reports that no rows are pending or excluded, then picks out the 7 Everyday Checking rows. They are all money out, so the preview shows the balance going down by $247.31, with categories such as Groceries and Transit. The Rewards Card rows stay out. After you say yes, it reports 7 rows saved.
For the second, your AI reports that all 14 rows are posted and none are excluded, with 7 rows for Everyday Checking and 7 for Rewards Card. Nothing is saved.
What carries over
Each row brings its date, amount, payee, category text, currency and notes. If one of your Pennyweight rules matches a row, the rule's category replaces Copilot's when the import is saved, unless you ask your AI to import with rules turned off. Copilot's parent categories, transaction types, recurrings and budgets don't move. See the full list of what doesn't move.
Good to know
- Your AI does the reading. Pennyweight has no Copilot importer. Your AI turns each line into a row with a YYYY-MM-DD date, a signed amount and a payee.
- Let your AI read the export, not a direct upload. Pennyweight can also read a CSV uploaded straight to it, but that route doesn't skip pending rows and doesn't split the file by account. Let your AI prepare each batch.
- One account per import. Each import goes into a single account. Pennyweight doesn't read the account column: your AI sends one batch per account.
- Each category is a single label. Each Copilot category arrives as one label, since categories have no parent and child levels in Pennyweight. Your AI can map them onto the names you want before saving.
- Internal transfers. If a transfer shows up in both accounts, each side goes into its own account. Then ask your AI to find the pairs and link them. See link transfers.
- Budgets. Ask your AI to create your budgets again. See set a budget.
- Rules don't move. Ask your AI to recreate the rules you rely on. See rebuild your rules after moving.