The Scenario
You are a RevOps analyst. Your company is switching CRMs and you have three weeks to migrate 85 open deals from your legacy system into Fireberry before the old system goes dark. The deals live in a Google Sheet that came from a Salesforce export: deal name, estimated value, close date, stage, and the name of the account each deal belongs to.
The Fireberry import wizard is not going to work cleanly. Salesforce account names do not match Fireberry account names, the stage names are different between the two systems, and the close dates came through as text strings in the export.
The system switchover is in three weeks. You do not have time to clean 85 rows manually and hand-enter them one by one.
The bad version of this project:
- You start with the Fireberry import wizard
- It rejects 40 rows because the account names do not match
- You manually search Fireberry for each account and update the spreadsheet column
- You re-import
- It rejects 12 more rows because the stage values are not in Fireberry's accepted stage list
- You look up the stage mapping, update those rows, re-import again
- You finish with 73 of 85 deals successfully imported
- The other 12 failed silently and you do not realize it until the go-live date
The fast version is one prompt.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent inside your spreadsheet that handles the account name matching, the stage mapping, and the opportunity creation, and writes the result back to the sheet so every row is accounted for.
Open the SheetXAI sidebar and type:
Create a Fireberry opportunity for each row in this sheet using column A for deal name, column B for estimated value, column C for close date, column D for stage, and column E for account name. For each row, match the account name to the closest Fireberry account using a name search. Write the created opportunity GUID into column F and the matched Fireberry account GUID into column G. If no account match is found, write "No match — review" into column G and skip the opportunity creation for that row.
SheetXAI creates the opportunities, links them to the right accounts, and gives you a sheet where column F confirms every successful creation and column G shows you which account it was linked to. Any "No match" in column G is an explicit flag to investigate, not a silent failure.
What You Get
A migration audit sheet:
- Column F — Fireberry opportunity GUID for each successfully created deal
- Column G — the Fireberry account GUID it was linked to, or "No match — review" for rows that need attention
- 85 rows accounted for — every row has an outcome, nothing is silently skipped
Failed rows are explicit. You know exactly which deals did not get created and why, before go-live.
What If the Data Is Not Quite Ready
Legacy CRM exports have predictable mess patterns.
When the stage names from Salesforce do not match Fireberry's stage list
Your Salesforce export has "Needs Analysis" but Fireberry uses "Qualified."
Before creating the Fireberry opportunities, remap the stage values in column D using this mapping: "Needs Analysis" → "Qualified", "Value Proposition" → "Proposal", "Perception Analysis" → "Negotiation", "Id. Decision Makers" → "Prospecting". Then create opportunities using the remapped stage values. Write GUIDs into column F.
When close dates are text strings instead of dates
The Salesforce export formatted close dates as "2026-09-30" text strings, not Excel-compatible dates.
Convert the values in column C to proper dates before creating the Fireberry opportunities. Then proceed with the creation, matching accounts by name, and write GUIDs into column F.
When some deals have an estimated value of zero because they were logged before negotiation
About ten rows have value at zero. You want those created but flagged for follow-up.
Create Fireberry opportunities for all rows. For rows where column B is zero or blank, create the opportunity with a zero value and add the note "Value TBC" in the Fireberry description field. Write GUIDs into column F. Also write "Zero value — follow up" into column H for those rows so the sales team can see them clearly.
When you need the full migration: remapping, date conversion, account matching, and a final audit in one pass
For each row in this sheet: convert column C close dates from text to date format, remap column D stage names using this mapping (list your mapping), search for the matching Fireberry account by name in column E, create the opportunity with all five fields, and write the opportunity GUID to column F and account GUID to column G. After all rows, write a summary to a new 'Migration Summary' sheet: total opportunities created, total accounts matched, total rows with no account match, and a list of the no-match rows with their deal name and account name.
The pattern: the migration is a spreadsheet problem. You describe the rules once and SheetXAI applies them across all 85 rows.
Try It
Get the 7-day free trial of SheetXAI and use it to migrate your next deal list into Fireberry in one pass. The Fireberry integration is included in every plan. For related workflows, see how to export your live Fireberry pipeline for forecasting or the Fireberry in Google Sheets overview.