Bring your old Mint export into Pennyweight

Mint has moved to Credit Karma: its site now says it has been reimagined there. If you downloaded your Mint transactions before the move, you can still bring that history into Pennyweight. Your AI reads the file and sends the rows to Pennyweight, one account at a time, and nothing is saved until you approve a preview. New to importing? Start with how importing works.

Before you start

Find the CSV file you downloaded from Mint. Open it and check three things, because your AI needs to know them:

• The accounts. If each line names its account, note the account names. Each one needs a home in Pennyweight.
• The signs. If the amounts have no minus sign and a separate column says debit or credit, that column gives the direction. Debit is money out and credit is money in.
• The row count. Count the transaction lines, leaving out the header. You'll compare it with what gets imported.

How to do it

1. Share the CSV with your AI.
2. Tell it which Pennyweight account each Mint account goes into. A file that mixes accounts is split by your AI into one batch per account. To bring in only some accounts, say which.
3. Tell it how the file signs amounts. Pennyweight stores money out as negative and money in as positive, so your AI turns each debit into a negative amount and each credit into a positive one.
4. Your AI converts each date to YYYY-MM-DD form. Rows your AI sends to Pennyweight must use that format.
5. 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.
6. Give your AI the row count. It passes the count with each batch, and Pennyweight refuses a batch whose rows don't match it, so a dropped line can't slip through.
7. Your AI shows a preview for each account: new rows, likely duplicates and rows that need a look. Nothing is saved yet. Check that each balance moves the way you expect. See reading an import preview.
8. Say yes to import, then work through after you import.

What you'll see

For the first prompt, your AI reports 14 rows: 7 for Everyday Checking and 7 for Rewards Card. The Everyday Checking preview shows 7 rows of money out, and the balance going down by $247.31. The Rewards Card preview shows 3 rows of money in, totaling $2,164.34, and 4 rows of money out, totaling $152.51. After you say yes, it reports 7 rows saved in each account.

For the second, your AI lists Everyday Checking with 7 debits and no credits, and Rewards Card with 4 debits and 3 credits. 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 Mint's when the import is saved, unless you ask your AI to import with rules turned off. If your file has a Labels column, those labels don't move, and neither do budgets or rules. See the full list of what doesn't move.

Good to know

• Your AI does the reading. Pennyweight has no Mint 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 file, not a direct upload. Pennyweight can also read a CSV uploaded straight to it. That route reads an unsigned amount next to a column that says debit or credit, and converts dates like 9/02/2026 when your AI names the date order. It doesn't split a file by account, so a file that mixes accounts needs your AI to read it.
• One account per import. Each import goes into a single account. Pennyweight doesn't read the account column: your AI uses it to split the file and sends one batch per account.
• Each category is a single label. A row's Mint category arrives as one label. Your AI can map the labels onto the names you want before saving.
• Labels can be added again. Imported rows carry no tags. After the import, your AI can tag transactions in Pennyweight.
• Transfers between your accounts. If a transfer shows up in both accounts' rows, each side goes into its own account. Then ask your AI to find the pairs and link them. See link transfers.
• Many accounts or years of history. Ask your AI to plan the import first. The plan lists each account in the file, whether it matches one you already have, and the batches to import. See import years of history across many accounts.
• Rules don't move. Ask your AI to recreate the rules you rely on. See rebuild your rules after moving.