Add deals by pasting JSON
Create several deals at once, with their value, stage, status, owner, people and notes, by pasting a JSON document.
Import deals… adds deals from a JSON document, such as one an assistant writes from a spreadsheet or from another sales tool's export.
- In Deals, select More and then Import deals….
- Choose Copy the prompt. It copies this format with the instructions an assistant needs.
- Give the assistant the prompt and what you are working from.
- Paste its answer into the box and choose Import deals.
Magpie does not read a CSV file directly. Give the exported rows to the assistant with the prompt, and import the JSON it writes.
Importing only adds deals. It never changes a deal that is already there. The same document imported twice is imported once.
The whole document is checked before anything is saved. If any part of it
does not fit the format below, no deals are added and the problem is
reported with the exact field that caused it, such as deals[2].stage.
The document
{
"deals": [
{ "name": "Northline office fit-out", "value": 18000, "stage": "Proposal" }
]
}
deals is required. It holds at least one deal and at most
200.
Each deal
| Field | Type | Notes |
|---|---|---|
name |
string, required | What the deal is called. |
value |
number, optional | The amount in the currency's main unit, such as 18000 or 18000.50. Zero or more. |
currency |
string, optional | A three-letter code, such as USD. The team's currency if left out. |
pipeline |
string, optional | The name of one of the team's pipelines. The default pipeline if left out. |
stage |
string, optional | The name of a stage of that pipeline. Its first stage if left out. |
status |
string, optional | open, won or lost. open if left out. |
lostReason |
string, optional | For a lost deal: the name of one of the team's lost reasons. The last reason in the team's list if left out. |
expectedCloseOn |
string, optional | A date, YYYY-MM-DD. |
owner |
string, optional | The email address of a team member who can edit in Deals. Nobody if left out. |
people |
array, optional | The people the deal is with. See below. |
notes |
string or array of strings, optional | One note, or several. Newlines are kept. |
createdOn |
string, optional | The day the deal was first made, YYYY-MM-DD, not in the future. Today if left out. |
closedOn |
string, optional | For a won or lost deal: the day it was closed, YYYY-MM-DD. Not in the future and not before createdOn. |
A pipeline, stage or lost reason is matched by its name, whatever its capitals. One the team does not have is refused by name and nothing is added: add it in Deals settings first. A field that is not in this table is refused too.
A won or lost deal keeps the stage you name, which is the stage it was in when it closed.
People
Each entry of people has a name, an email, or both, and may have a
company:
{ "name": "Dana Ortiz", "email": "dana@northline.example", "company": "Northline" }
A deal has up to 20 people. The first is the deal's main person.
Someone whose email address is already a contact is matched to that contact, which is not changed. Anyone else is added to Contacts, within your plan's limit on contacts. The message after the import says how many deals and how many contacts were added.
A longer example
{
"deals": [
{
"name": "Northline office fit-out",
"value": 18000,
"currency": "USD",
"pipeline": "Sales",
"stage": "Proposal",
"expectedCloseOn": "2026-12-12",
"owner": "sam@example.com",
"people": [
{ "name": "Dana Ortiz", "email": "dana@northline.example", "company": "Northline" }
],
"notes": ["Budget is approved for this quarter."],
"createdOn": "2026-10-01"
},
{
"name": "Harbourfront signage",
"value": 4200,
"stage": "Negotiation",
"status": "lost",
"lostReason": "Price",
"createdOn": "2026-09-14",
"closedOn": "2026-10-20"
}
]
}
If an import is rejected for a reason you can't work out, Contact support.
Ask Magpie support
Send Magpie staff a question about anything this article does not answer.