Sync Monarch Money balances to ProjectionLab.
Chrysalis is a Chrome extension that pulls your live account balances from Monarch Money and pushes them into ProjectionLab with one click. No scripts, no terminal, no copy-pasting numbers by hand.
Chrysalis is, and will always be, free to use. But if you want to say thank you, coffee is my love language.
ProjectionLab is a powerful financial planning tool, but it need an accurate starting point for projections. Monarch Money knows exactly what your accounts are worth. Chrysalis serves as the bridge between the two, so your plan stays grounded in your actual balances without manual data entry.
There are a couple of workarounds floating around the internet, but they had various issues and I wanted a full-service product experience... so I built it. My goal with Chrysalis is to make a full-featured, polished integration between Monarch and ProjectionLab.
- Google Chrome or a Chromium browser (I like Dia)
- A Monarch Money account
- A ProjectionLab account with Plugins enabled
- Your accounts must already exist in ProjectionLab (Chrysalis updatesPL balances, it cannot create accounts)
Chrysalis is available on the Google Chrome Web Store. Just click "Add to Chrome" to get started.
The Chrysalis icon will appear in your Chrome toolbar. Pin it for easy access.
Setup takes about two minutes and only needs to be done once. Before you ever configure your settings, the popup will indicate that setup is required.
Click the Chrysalis icon and then click Setup ↗ in the top-right corner of the popup to open the setup page.
Chrysalis uses ProjectionLab's official Plugin API to update your account balances. You need to enable this and generate a key:
- Log into ProjectionLab
- Go to Account Settings (top-right menu) → Plugins
- Toggle Enable Plugins on
- Copy the value shown in the Plugin API Key field
Paste it into the API key field in Chrysalis and click Save Key.
Before you can map anything, Chrysalis needs to fetch your account lists from both services.
- Make sure you're logged into Monarch Money. Have
app.monarchmoney.comopen in a tab - Click Load Accounts from Monarch. You should see success text underneath the button
- Make sure you're logged into ProjectionLab in an open tab
- Click Load Accoungs from ProjectionLab. You should see success text underneath the button
- Anytime you add/remove/rename accounts in either tool, come back to Setup the click the corresponding buttons, which will then say "Refresh Accounts from Monarch/ProjectionLab". Your mappings are keyed by ID and will be preserved even if you change the name of an account.
This is where you tell Chrysalis which Monarch account corresponds to which ProjectionLab account.
Each row represents one ProjectionLab account (the destination). On the left side, you select one or more Monarch accounts to map to it.
One-to-one mapping (most common): select one Monarch account on the left, one ProjectionLab account on the right.
Many-to-one mapping: if you have multiple Monarch accounts that should roll up into a single ProjectionLab account — for example, two checking accounts that map to one "cash" entry — select all of them on the left. Chrysalis will sum their balances before syncing.
To add a mapping:
- Use the + add Monarch account dropdown to select a Monarch account — it will appear as a chip
- Add more Monarch accounts to the same row if needed
- Select the corresponding ProjectionLab account on the right
- Click + add PL account mapping to add another row for a different PL account
Mappings are saved automatically. When a row is completed, a green checkbox appears on the right indicating it has been saved. When all ProjectionLab accounts have been mapped, a green success message appears at the bottom of the section and the "Add ProjectionLab account mapping" button is hidden.
You are not required to map every account, only map the ones you want Chrysalis to sync.
When your setup is complete, you'll see green visual feedback indicating each section is done, as below:
Special mapping for assets: Monarch and ProjectionLab work differently in terms of how the data is structured for various types of assets (real estate, cars, motorcycles, jewelry, precious metals, etc.). Monarch stores an asset's value and a loan against that asset as 2 separate accounts, while ProjectionLab has both the value of an asset and a loan against an asset in 1 account. Don't fret, the mapping of this kind if asset is fully supported.
When you select a ProjectionLab account that is one of these asset types, the row switches to a 2-lane layout that supports both the Asset and the Loan amount for that ProjectionLab account. On the Monarch side, you choose the Asset and Loan accounts individually. When synced to ProjectionLab, the Asset and Loan amounts from the 2 separate Monarch accounts are automatically merged into the 1 ProjectionLab account in the correct target fields.
Once setup is complete, syncing is a one-step process:
- Navigate to
app.monarchmoney.comin Chrome (and make sure you're logged in) - Click the Chrysalis icon in your toolbar
- Click Sync Now
The sync button is only active when you're on the Monarch site. This is intentional — Chrysalis reads your session directly from the Monarch page, so the page needs to be open. If you're on a different tab and click the popup, it instructs you to go to a Monarch tab first before you can sync, as seen here:
After you have at least 1 sync in the cache, the popup will also include details about the past syncs. An expandable gray section appears showing you the most recent sync job that occurred. You also have links out to each sync in memory in the table below. Clicking View History opens the Sync History page, while clicking a row in the table opens that specific record.
Chrysalis does not store your Monarch username or password. Instead, it reads the session token that Monarch's web app stores in the browser's localStorage after you log in normally. This is the same token your browser is already using to show you your accounts — Chrysalis just borrows it. This approach is both more secure and more reliable than storing credentials.
Once it has the session token, Chrysalis makes a GraphQL request directly to Monarch's API, the same endpoint the Monarch web app uses, and retrieves the current balance for each of your mapped accounts.
Chrysalis calls ProjectionLab's official Plugin API for each mapped account, sending the current balance. If you have multiple Monarch accounts mapped to one ProjectionLab account, Chrysalis sums the balances first, then makes a single API call with the total.
Everything. Your API key is stored in Chrome's extension storage. Your account mappings are stored there too, and sync across your Chrome profiles if you're signed into Chrome. No data is sent to any server other than Monarch and ProjectionLab's own APIs.
After each sync, the popup shows a per-account breakdown:
- ✓ Each successfully updated account, with the balance that was written and the Monarch source(s) it came from
- ✗ Any accounts that failed, with the specific error
- ⚠ A warning if some (but not all) source accounts in a many-to-one mapping couldn't be found — Chrysalis will still sync using the accounts it could find
The result list stays visible until you run the next sync, so you can close and reopen the popup without losing the last run's details. The most recent sync section collapses after 5 seconds, but you can always re-expand it as you like.
Click View History on the setup page, or the same link in the extension popup when you are on a Monarch tab. The Sync History keeps a log of recent syncs with timestamps and outcomes including the Monarch accounts synced to which ProjectionLab target accounts, the amount that was synced (positive or negative), and a status of that account's sync job. Useful for confirming a sync ran correctly or diagnosing a pattern of failures. The most recent Sync History shows up under a collapsed gray section on the popup after you have run at least 1 sync.
If one of your mapped accounts is deleted or hidden in Monarch after you set up a mapping, Chrysalis will:
- Skip that account with an error rather than writing a wrong balance
- Still sync all other accounts that resolved correctly
- Report partial success so you know something needs attention
The Advanced section lives at the bottom of the setup page. It's collapsed by default and intended for diagnostics and data management. You won't need it during normal use.
To help ensure people don't accidentally take an unreversible action on their Chrysalis instance, the Advanced section is locked. Click "Unlock Advaned Settings" to enable the section, and it can be re-locked when you're done.
This checkbox will inject more detailed, technical debug details in 2 places: (1) on the extension popup after a sync job has run, and (2) at the bottom of any sync record under Sync History. If something is wonky, this is a good place to start.
If you want to, you can enable a time-based sync job daily, weekly, monthly, or quarterly, and you can choose the day or week or day of month and time of day for it to run. Note: The scheduled job will only work if the base conditions are met for processing, being that you must have Google Chrome open, your computer awake, and a Monarch tab must be open in your browser in an active session.
If you want to automatically clear out your sync history data based on their age, you can use this as a TTL (time-to-live) setting. Enter the number of days that is the acceptable age of sync history records. When they have passed this age, they will be automatically deleted when the next sync job runs. If you leave this blank, records will be retained forever (or, until you manually delete them - see below).
This button does just that. It clears your API key, account mappings, and cache all in 1 click. This is effectively a full reset.
This button clears your cache, including sync history and account lists. Your account mappings and API key are retained.
This button only clears your account mappings, but keeps your API key and cother cached data in place.
This section has 2 buttons: one to download your current mappings as a JSON file, and another to upload mappings. This is useful if you need to migrate your Chrysalis settings from one computer to another. Or, if you are someone who clears your cache a lot if for software development purpuoses or what have you, then you might want to keep your account mappings saved to your local machine to re-upload when you're ready to sync again. The upload takes <1 second, and replaces any pre-existing mappings that may be there.
"No Monarch session token found"
Make sure you're logged into Monarch Money in the current tab. Try refreshing the Monarch page and syncing again. If you're still having issues, go to the Advanced section under Setup and click the "Run Monarch diagnosis" button. It will generate some text that should help you solve the issue.
"ProjectionLab plugin API not found"
Plugins are not enabled in your ProjectionLab account. Go to Account Settings → Plugins and toggle them on. If ProjectionLab still won't connect after your API key is enabled and entered in Setup, then go to the Advanced section under setup and click the "Run ProjectionLab diagnosis" button. It will generate some text that should help you solve the issue.
Balances look wrong after sync
Check the sync result detail in the popup — if a many-to-one mapping is partially resolving (some source accounts missing), the balance shown will be lower than expected. Update your mappings to reflect your current Monarch accounts.
Still stuck, or something looks like a bug? Open an Issue on the GitHub repo.
- Chrysalis requires the Monarch tab to be open when syncing. This is a trade-off for not needing to store your credentials.
- ProjectionLab accounts must already exist. Chrysalis cannot create new accounts, only update balances on existing ones. This is a limitation of the ProjectionLab API which does not expose any "create account" method.
- This uses Monarch's internal GraphQL API, which is unofficial and unversioned. It could change without notice. See Contributing for how to report or fix breakage.
Contributions are welcome, especially fixes when Monarch or ProjectionLab change their APIs.
When Monarch breaks auth or account fetching, the relevant file is content-scripts/monarch.js. The most common failure mode is that the session token could move to a different localStorage key. The token scanning logic is at the top of that file.
When ProjectionLab's Plugin API changes, the relevant call is in background/service-worker.js.
When you open an Issue, please include:
- What error you saw (exact text)
- Whether the Monarch web app itself was working normally at the time
- Your Chrome version
Chrysalis is an independent project and is not affiliated with, endorsed by, or supported by Monarch Money or ProjectionLab. It uses unofficial APIs that may change at any time. Use it at your own risk, and always keep a backup of your ProjectionLab data (Account Settings → Export Data) before syncing.
MIT