GTM Systems Health ConsoleViewing as: GTM Systems (demo)
Shown with sample HubSpot and Salesforce data
GTM Systems Health ConsoleImports run the same way every time: prepare, map, dedupe, assign campaign and source, import, then verify.
File preparation, field mapping, campaign and source assignment, execution, and post-import verification.
MSP Security Roundtable - attendees.csvSampleCSV column → Salesforce field. Every column is mapped or deliberately left out.
| CSV column | Salesforce field | Check |
|---|---|---|
| First Name | First Name | |
| Last Name | Last Name | |
3 invalid addresses will be skipped | ||
| Company | Company | |
| Job Title | Title | |
| Company Size | Employee Range | |
| State | State/Province | 12 full state names converted to 2-letter codes |
| Country | Country | |
| Partner Type | Is MSP | “MSP” and “MSSP” → Yes |
| Attended | Campaign member status | |
| Notes | not imported | free text, kept in the source file |
Existing records are updated, not created again.
Current values for the 46 records that will be updated were saved: backup_2026-10-06_1035.csv
After the import you'll check expected against actual before it's logged.