Moving from PocketSmith

If you've been using PocketSmith, you can bring your transaction history into Pennyweight. You export your transactions from PocketSmith, and your AI reads the file, plans the import and sends the rows to Pennyweight, one account at a time. New to importing? Start with how importing works.

Export from PocketSmith

These steps are per PocketSmith's help center, and its menus can change.

• All transactions. Go to the Transactions page and select All transactions in the left-hand menu. Hover over Export in the toolbar and choose CSV or XLSX. The file is saved to your Downloads folder.
• All transactions, from Settings. Go to Settings, then User preferences, then Export data. Under the option to export all transactions to CSV, click Download a CSV.
• Only some transactions. On the Transactions page, search for the transactions you want, then hover over Export and choose CSV or XLSX.

How to do it

1. Share the export with your AI and ask it to plan the import before saving anything. The plan lists each account in the file, whether it matches an account you already have in Pennyweight, and the batches to import, of up to 250 rows each. Planning saves nothing.
2. Tell your AI which Pennyweight account each PocketSmith account goes into. If each line names its account, your AI uses that to split the file. Each import goes into one account, so your AI sends one batch per account.
3. If an account doesn't exist in Pennyweight yet, the plan says so, and your AI adds it first. A new manual account needs an opening balance before its first import: the balance just before the first row. For a credit card or loan, give what you owed as a positive number. See add a manual account.
4. For each batch, your AI shows a preview: new rows, likely duplicates, rows that need a look, and the account's balance after the import. Nothing is saved yet. Check that the balance moves the way you expect. See reading an import preview.
5. Say yes to import. Your AI reports how many rows were saved and any it skipped. Then work through after you import.

What you'll see

Your AI first shows the plan: each account in the file with its row count and date range, the Pennyweight account it goes into, and the batches. If an account already holds imported history, the plan warns you, so you can skip it or import only the dates you're missing. Then your AI converts the dates to YYYY-MM-DD, signs each amount from the account's side, and shows a preview for each batch. After you say yes, it reports the rows saved in each account.

What carries over

Each row brings its date, amount, payee, category text, currency and notes. Budgets, tags and labels, attachments and category groups don't move. See the full list of what doesn't move.

Good to know

• Your AI does the reading. Pennyweight has no PocketSmith importer. It can read a CSV uploaded straight to it, but that route puts the whole file into one account, and it converts dates not written as YYYY-MM-DD only when your AI names their order. When your AI reads the export, it splits the rows by account and converts the dates itself.
• Check the signs. Pennyweight stores money out as negative and money in as positive. On a card, a charge is negative and a payment is positive. The balance in each preview shows whether your AI got the direction right.
• Closing balances help. If you know an account's balance at the end of the export, give it to your AI for the plan. After the last batch, your AI checks the account's balance against it.
• Linked bank accounts. If an account is already linked to your bank in Pennyweight, the history goes into that same account. Pennyweight already holds the bank's recent history, so import only the dates before it. Then your AI sets the opening balance so the account matches the bank's balance.
• Categories come over unless a rule matches. Each row keeps its PocketSmith category as a single label. Your active Pennyweight rules run when the import is saved, and a matching rule's category replaces the one from the file. The preview shows how many rows your rules would change. To keep every PocketSmith category as it is, ask your AI to import with rules turned off. Your AI can also map categories onto the names you want before saving.
• Transfers appear in both accounts. A card payment from checking shows up on both sides. Import each side into its own account, then ask your AI to find the pairs and link them. See link transfers.
• Many accounts or years of history. The plan handles up to 100 accounts. See import years of history across many accounts.
• Your PocketSmith rules don't move. Ask your AI to recreate the ones you rely on. Rules you add after the import change rows already saved only when your AI applies them. See rebuild your rules after moving.