Faster spreadsheet intake
Recruiters can move from a file to usable CRM records with fewer repetitive mapping decisions.
July 2026 Data import
AI-Powered CSV Import
ATZ CRM added AI-powered CSV import so recruiters can map spreadsheet columns to CRM fields faster and bring bulk data into the workspace with fewer setup errors.
Automatically suggest CRM field matches for spreadsheet columns
Reduce manual mapping work during bulk imports
Help admins spot field mismatches before records are created
Speed up candidate, contact, company, and job data movement
Support cleaner imports when teams migrate or refresh data
Quick answer
What changed for recruiters?
AI-Powered CSV Import helps recruiters and admins upload spreadsheets with less manual field mapping. ATZ CRM can suggest the right CRM fields for columns in a CSV or spreadsheet file, letting teams review the mapping, confirm it, and move candidate, contact, client, or job data into the system faster.
What changed
What this update changes
ATZ CRM now uses AI to help map spreadsheet columns to the correct CRM fields during CSV import. Instead of manually matching every column one by one, recruiters and admins get suggested field matches that they can review before completing the upload.
The update is especially useful when files arrive from different sources: old ATS exports, client spreadsheets, job board lists, event registrations, sourcing projects, or agency-owned databases.
AI mapping does not remove the need for review. It gives the team a faster first pass, then the admin can confirm field choices, check required data, and decide whether the file is ready to import.
Cleaner mapping at the import stage helps downstream workflows such as search, matching, reporting, segmentation, and follow-up because important details land in the right fields from the beginning.
Why it matters
Why it matters to recruiters
Recruiters are often measured on speed, quality, and follow-through. This update is designed to reduce manual work, protect useful context, and help teams keep hiring activity moving with fewer handoffs.
Fewer import mistakes
Suggested mappings help teams catch columns that may otherwise be assigned to the wrong field or skipped during upload.
Better database quality
When fields are mapped correctly, records become easier to search, filter, match, assign, and report on later.
Smoother migrations and cleanup projects
Admins handling legacy data can move more confidently through large files while still checking the final import choices.
Before and after
How the workflow changes
Before
Admins manually matched spreadsheet columns to CRM fields and checked long files column by column.
After
ATZ CRM suggests field mappings so the team can review, adjust, and confirm the import setup faster.
Before
Different spreadsheet formats slowed down imports because column names varied across sources.
After
AI mapping gives recruiters a stronger starting point even when files use different naming conventions.
Before
Poor field mapping could create cleanup work after records were already imported.
After
Teams can inspect mapping suggestions earlier and reduce rework before the upload is completed.
How recruiters use it
How the workflow works
The exact setup depends on your workspace and permissions, but the core workflow is built to keep recruiters closer to the record, the next action, and the right team context.
1
Prepare the import file
Review the spreadsheet for obvious duplicates, missing required details, and columns that should become searchable CRM fields.
2
Upload the CSV or spreadsheet
Start the import flow and let ATZ CRM inspect the file structure.
3
Review AI-suggested mappings
Check whether names, emails, phones, organizations, skills, owners, stages, and custom fields are matched correctly.
4
Adjust anything sensitive
Manually correct field choices when the data affects ownership, compliance, communication permissions, or reporting.
5
Complete the import and audit results
Finish the upload, then review the created records so recruiters can trust the imported data during daily work.
Feature-specific details
Extra context for this update
Some releases affect more than one recruiting workflow. These notes explain the practical details recruiters, admins, or managers may want to review before rolling the update out to the team.
Import quality
Fields recruiters should check before confirming a mapped file
AI mapping is a speed layer, but the best imports still depend on recruiter and admin review before records enter the database.
Identity fields
Confirm name, email, phone, LinkedIn URL, organization, and source fields because these affect duplicates and communication.
Recruiting context
Check skills, job titles, work history, tags, folders, owner, and stage values so records can be filtered after upload.
Custom fields
Review agency-specific fields carefully because the AI may not know your internal naming habits without admin review.
Consent and opt-out fields
Treat communication preferences with extra care before any imported list becomes part of outreach workflows.
Best fit
Teams that benefit most
Recruiters importing sourced candidate lists
Admins moving data from older recruitment systems
Agencies uploading client, contact, or company spreadsheets
Teams refreshing database records after campaigns or events
Operations users responsible for clean import mapping
Helpful next steps
Related ATZ CRM pages
Import CSV and XLS files Review the standard spreadsheet import workflow before using AI-assisted mapping. Import organizations and contacts See how company and contact files can be brought into ATZ CRM with cleaner relationships. Import Candidate and Client Data Explore how ATZ CRM supports bulk movement of recruiting records into one workspace. Bulk Import for Contacts and Organizations Read the earlier release that expanded high-volume contact and organization intake. Merge Candidates and Contacts Use merge workflows after imports when duplicate people or records need cleanup.
Quick answers
Common questions
What does AI-Powered CSV Import do?
It suggests CRM field matches for spreadsheet columns so recruiters and admins can review and confirm imports faster.
Can recruiters still change the field mapping?
Yes. The AI suggestion is a starting point, and users should adjust any field that does not match the file correctly.
Which files benefit most from AI mapping?
Files with many columns, unfamiliar headings, legacy exports, or mixed candidate and client information benefit most.
Does this prevent every import duplicate?
No. Better mapping helps, but teams should still review duplicate rules, unique identifiers, and merge needs after import.
Why does field mapping matter after the import?
Correct fields make records easier to search, segment, match, report on, and use in outreach workflows.
Should admins review AI-mapped custom fields?
Yes. Custom fields often reflect agency-specific language, so admin review is important before completing the upload.
See it in context
Review this update inside your recruiting workflow
Book a walkthrough with the ATZ CRM team to see how this update supports your jobs, candidates, and shortlist process.