The Scenario
You're the marketing ops engineer leading a platform migration. The kickoff call with the new ESP's onboarding team is tomorrow at 9 AM, and they've asked for a full inventory of your UniSender custom contact fields — ID, name, data type, visibility — so they can map them against the destination schema before the migration window opens. You have 47 fields in the account. You have an Excel workbook and a morning.
The bad version:
- Open UniSender settings, navigate to custom fields. The UI lists field name and type. The field ID is not shown — you have to click into each field individually to find it.
- Click into field 1. Note the ID. Note the type. Note the visibility setting. Switch to Excel. Type them in.
- Repeat 46 more times. About halfway through, realize you've been copying the internal IDs, not the API field IDs the new platform actually needs. Go back and check which type they asked for.
- Finish the inventory. Send it to the onboarding team. Get a reply asking you to add a column for the field's public-facing label. It's already in the sheet — but it's the same as the internal name for most fields, except for six of them.
Three hours to document something that lives in a database.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Excel workbook. It pulls full custom field definitions directly from UniSender's API in a single 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 Excel sheet. Add headers in row 1, start data in row 2.
What You Get
- One row per custom field, all 47 covered.
- Field IDs, public names, types, and visibility in labeled columns.
- A worksheet your new platform's onboarding team can use directly.
- Done before the 9 AM call instead of during it.
What If the Data Is Not Quite Ready
The new platform only accepts public fields
List all UniSender custom contact fields where visibility is "public." Write field ID, public name, and data type into my Excel sheet. Skip any internal fields.
You need a blank column for the destination schema mapping
List all UniSender custom contact fields. Write field ID, public name, and data type into columns A, B, and C. Leave column D blank for the Salesforce field mapping I'll fill in manually.
Flag types that don't exist in the destination schema
List all UniSender custom contact fields. Write field ID, public name, and data type into my Excel sheet. Add a "needs_review" column and mark any field whose type is not one of: text, number, date, boolean.
Full migration documentation in one pass
List all UniSender custom contact fields. Write field ID, public name, data type, and visibility. Sort by data type ascending. Add a blank "destination_field" column for manual completion. Flag any field with a name longer than 30 characters in a "rename_needed" column.
Try It
Get the 7-day free trial of SheetXAI and open a blank Excel workbook before your next migration kickoff — ask it to document your UniSender field schema in whatever format the destination platform needs. See also: export email templates before migration or the full UniSender overview.