The Scenario
The legacy helpdesk contract ends Friday. You have 300 tickets exported to a Google Sheet — Subject, Description, Priority, Status, all in columns A through D — and every one of them needs to exist as a Salesforce case by Thursday morning so the support team can pick up where they left off without missing a beat.
You open Salesforce and stare at the case creation form. One at a time.
The bad version:
- Copy the subject from row 2, paste it into the New Case form, fill in description and priority, save, copy the case ID back into column E, move to row 3.
- Repeat 299 more times, losing your place around row 80 when a required field throws a validation error and you're not sure which rows succeeded before it.
- Spend the last two hours before the deadline manually reconciling which rows got IDs and which ones silently failed.
You are not a data entry contractor. Nobody hired you to do this. The actual work — making sure the cases are correctly categorized and assigned before the team inherits them — is sitting untouched while you copy-paste.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads your data and talks to Salesforce Service Cloud directly, so you can describe what you want done and it handles the API side.
Create a Salesforce Service Cloud case for every row in this sheet — column A is Subject, column B is Description, column C is Priority, column D is Status; write the returned Case ID into column E
What You Get
- A case created in Salesforce for each row, with Subject, Description, Priority, and Status mapped from your columns.
- The Salesforce-generated Case ID written into column E for each successful row.
- Rows that fail (validation errors, missing required fields) get an error message in column E instead of silently disappearing.
- A count of successes and failures at the end so you know exactly what landed.
What If the Data Is Not Quite Ready
Priority values don't match Salesforce's picklist options
Your sheet has "Urgent" but Salesforce expects "High." Half the rows will fail validation.
For each row in this sheet, before creating the Salesforce case, normalize column C so that Urgent maps to High, Low maps to Low, and anything else maps to Medium — then create the case with the corrected Priority and write the Case ID into column E
Some rows are already migrated from a previous partial run
Column E has Case IDs for the first 100 rows. You don't want duplicates.
For each row in my sheet where column E is blank, create a Salesforce Service Cloud case using Subject from column A, Description from column B, and Priority from column C, then write the returned Case ID into column E
Description field contains HTML from the old system
The exported descriptions have paragraph tags and anchor tags that will render as raw HTML in Salesforce.
Strip HTML tags from every value in column B, then create a Salesforce case per row using Subject (A), cleaned Description (B), Priority (C), and Status (D), writing Case IDs into column E
Full cleanup, dedup, and create in one shot
Descriptions have HTML, Priority values need normalizing, and you want to skip any row where column A is blank.
For every row where column A is not blank: strip HTML from column B, normalize column C (Urgent to High, anything unknown to Medium), create a Salesforce Service Cloud case with Subject (A), Description (B), Priority (C), Status (D), and write the Case ID or error into column E — skip rows where column A is empty
One prompt. The cleanup and the create happen inline, together.
Try It
Get the 7-day free trial of SheetXAI and open the migration sheet you've been dreading, then ask SheetXAI to create the cases. When you're done, see how it handles the escalation triage in the parent overview or the related spoke on pulling live case data with SOQL.