Migrate from monday.com to Thawly

Move your lost deals from monday.com to Thawly in 10 minutes. monday.com's sales CRM is built on top of its boards engine, so the export route is simply: filter your Deals board to lost rows, then Export to Excel from the more-actions menu.

What you need#

• A monday.com user with Edit access to the Deals board, plus the Export board to Excel permission. Most paid plans (Basic, Standard, Pro, Enterprise) include this for board owners and members; if you're a viewer you may need an admin to run the export.
• A modern browser. No monday.com API token, no GraphQL queries.
• About 10 minutes.

If your team uses monday.com Sales CRM (the dedicated CRM product), the workflow below applies as-is. If you're on classic monday.com Work Management with a custom-built deals board, the same export action works — your column names will just be whatever your team chose.

Step-by-step extraction#

1. Log in to monday.com at monday.com and switch to the workspace your sales board lives in.
2. Open your Deals board (or whatever your team named it).
3. Switch to the Main Table view if you're on the kanban or pipeline view — the table view is what you want for filtering and exporting. [Screenshot: monday.com board with view selector showing Main Table]
4. Apply filters using the Filter button at the top of the board:
   • Status → Lost (or your team's custom lost-status colour: monday.com encodes status as colour labels like green = won, red = lost, grey = open).
   • Pipeline (if you have one as a column) → your sales pipeline.
   • Optionally Close Date → In the last → 3 years.
5. Save the filtered view by clicking + Add view and name it Lost deals for Thawly. [Screenshot: monday.com board with filter panel and Save view dialogue]
6. Click the ⋯ (more actions) menu top-right of the board and choose More actions → Export board to Excel. [Screenshot: monday.com more-actions menu with Export to Excel highlighted]
7. monday.com generates a .xlsx file and downloads it directly (no email link).
8. Open the .xlsx in Excel or Google Sheets. Use File → Save As → CSV UTF-8 (Comma delimited) (*.csv) to convert it. Don't use the legacy CSV (Comma delimited) option in Excel — it drops the BOM and mangles non-ASCII characters in company names.

Field mapping#

Thawly's importer auto-maps any reasonable header. For reference:

• Company (or Account) column → name (used for Companies House matching)
• Deal Value → deal_value (GBP)
• Close Date (or Lost Date) → lost_date
• Lost Reason → lost_reason
• Custom Competitor column → lost_to
• Notes / Updates column → notes

monday.com's column model is flexible — your board may use a Text column, a Long Text column, or a People column for what other CRMs call "company". Whichever holds the company name is what Thawly needs in the name column. Rename the column in Excel before uploading if it's not obvious.

What to do with the Notes column#

Don't pre-clean. monday.com's Updates feed (the conversation thread attached to each row) often contains the richest data — call summaries, the AE's lost-deal post-mortem, the "tried again Q2 2025" comment. Add the Updates column to your export view if it isn't already there: it concatenates the most recent updates text into a single cell.

If your team uses a Long Text column for AE notes alongside Updates, include both. Thawly's AI summarises long activity logs and extracts structured signals (objection type, decision-maker title, competitor name, budget threshold) on its own. Editing notes by hand before upload is wasted work.

Common gotchas#

• Duplicate companies. monday.com boards don't enforce uniqueness — it's normal to have several rows for Linton Manufacturing Ltd if you've lost multiple deals with them. Thawly de-duplicates on lower-cased company name on import, so duplicate rows are safe.
• Currency mismatches. monday.com's Numbers column doesn't enforce a currency, so values are just numbers in whatever currency the AE used. If your team operates internationally, either tag a Currency column on the board and filter to GBP before exporting, or post-process the CSV in Excel.
• Multi-pipeline issues. Most monday.com sales setups use a single board for all deals, distinguished by a Pipeline column. Filter on the Pipeline column rather than trying to filter by stage names — stage names are reused across pipelines.
• Stale "won" or "open" deals. monday.com's Status column is colour-coded by label, not by a fixed schema. Filter on the exact label name (e.g. Status = Lost, not just Status = Red) — colours can be reused across multiple labels.
• Subitems hide important data. Some teams keep the Deal as the parent row and per-quote/per-version data as Subitems. The Excel export only includes parent rows by default. If your lost-reason or close-date data is on the subitem, expand the export to include subitems before downloading (under the export dialogue: tick Include subitems).

What happens next#

Drop the CSV at thawly.co.uk/upload. We auto-map the columns, run a Companies House lookup on every company name and show you a per-row preview before importing.

After import, monitoring runs on the next signal-source pass. Your first digest only lands when there's a real signal — see Reading your digest.

Coming from a different CRM?#

• Migrate from HubSpot — common landing place for teams who outgrow monday.com sales CRM.
• Migrate from Pipedrive — similar list-view export pattern, more deal-specific.
• Migrate from a spreadsheet — if you've already cleaned the data in Excel after the monday.com export.

For the bigger picture, read Dead deal recovery and Buying signals in B2B sales.