The Scenario
You're the marketing ops engineer responsible for an upcoming platform migration. The company is moving from UniSender to a new ESP, and the first thing the new platform's onboarding team asked for was a full inventory of all custom contact fields — names, IDs, data types, visibility settings — so they can map them against the destination schema before the migration begins. The migration is scheduled for three weeks from now. You have a kickoff call tomorrow at 9 AM.
The bad version:
- Log into UniSender, navigate to the contacts settings, find the custom fields section. Count: 47 fields.
- Start copying field names and IDs into a spreadsheet by hand — ID from one column of the UI, name from another, type from a dropdown you have to hover over to read.
- Realize the visibility setting (public vs. internal) isn't shown in the main list; you have to click into each field to find it. Click into all 47. Copy each one.
- Complete the inventory, share the sheet, and get an email from the new platform's team asking if the IDs you copied are field IDs or list field IDs. Go back into UniSender to check.
You've spent three hours documenting fields that exist in a database somewhere in UniSender's infrastructure. There's no reason for you to do this with a mouse.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads directly from UniSender's API and writes structured field documentation into your sheet in one operation.
List all custom contact fields in my UniSender account and write their field ID, public name, data type, and visibility (public or internal) into my Google Sheet. Add headers in row 1 and start data in row 2.
What You Get
- One row per custom field, covering all 47 (or however many you have).
- Field IDs, public names, data types, and visibility settings in labeled columns.
- A sheet your new platform's onboarding team can work from directly.
- Done in under a minute instead of three hours.
What If the Data Is Not Quite Ready
The new platform only accepts public fields — filter out internal ones
List all custom contact fields in my UniSender account where visibility is "public." Write field ID, public name, and data type into my Google Sheet. Skip any fields marked as internal.
You need to add a third column for Salesforce field mapping
List all custom contact fields in my UniSender account. Write field ID, public name, and data type into columns A, B, and C. Leave column D blank — I'll fill in the Salesforce mapping manually.
The migration team wants to know which fields have no matching type in the destination schema
List all custom contact fields in my UniSender account. Write field ID, public name, and data type into my Google Sheet. Add a column "needs_review" and mark any field whose type is not one of: text, number, date, boolean.
Full migration-ready documentation in one pass
List all custom contact fields in my UniSender account. Write field ID, public name, data type, and visibility into my Google Sheet. Sort by data type ascending, add a "Salesforce equivalent" column left blank for manual completion, and flag any field with a name longer than 30 characters in a "rename_needed" column.
The pattern: pull the field inventory and prep the documentation for the next step in the same prompt.
Try It
Get the 7-day free trial of SheetXAI and open a blank Google Sheet before your next migration kickoff, then ask it to document your UniSender custom field schema in whatever format your destination platform needs. See also: export email templates before migration or the full UniSender overview.