CSV imports are easy to underestimate.
The file opens in a spreadsheet, the rows look readable, and the cleanup seems small. Then the CRM import creates bad owner assignments, duplicate contacts, broken source reporting, or lifecycle values that do not match the dashboard.
Here is the QA checklist I would use before uploading a cleaned sales ops CSV.
1. Preserve IDs and rollback fields
Before cleanup, keep the raw file.
Do not overwrite:
- CRM record IDs
- email addresses
- owner identifiers
- account IDs
- source record IDs
- created dates
If the import fails, these fields are usually needed for rollback or deduplication.
2. Validate required fields
Before upload, check whether each row has the fields the destination system expects.
Common required fields:
- company
- owner
- lifecycle stage
- lead source
- record ID
- account ID
Missing required fields should be flagged, not guessed.
3. Normalize source labels
Source labels often drift over time:
PPC
Paid Search
paid search
Google Ads
Adwords
If these values enter the CRM as separate labels, reports become harder to trust.
Create a mapping table:
raw_value | approved_value | rule | review_needed
4. Check owners before upload
Owner fields affect routing and visibility.
Look for:
- inactive owners
- old rep names
- initials instead of approved user names
- team inboxes
- blank owners
Rows with uncertain owners should go into review.
5. Separate exact duplicates from possible duplicates
Do not deduplicate only by name.
Better signals:
- CRM ID
- account ID
- company domain
Name-only matches should usually be possible duplicates, not automatic merges.
6. Test a small batch
Before the full upload, test a small file with:
- one normal row
- one duplicate candidate
- one missing owner
- one unusual source label
- one lifecycle edge case
This catches validation problems without damaging the full dataset.
I keep a more complete checklist here:
The goal is not to make the CSV perfect. The goal is to make the import safe enough that the team can understand what changed and roll back if needed.
Top comments (0)