CRM Imports
Import contacts, accounts, and deals from CSV files.
Use imports when you are moving CRM data from another system or spreadsheet.
Import contacts, accounts, and deals in the order their relationships need. For example, import accounts before contacts when contacts should link to companies, and import contacts before deals when deals should link to people.
Before You Import
Clean the CSV first. Make sure required fields exist, email addresses are valid, company names are consistent, and duplicate records are removed where possible.
Create a backup of the source spreadsheet before editing it. Keep only the rows you want to import and remove old notes, hidden columns, formulas, and test data.
Prepare related records before importing. Create pipelines and stages before deal imports, custom fields before mapping custom data, and accounts before contacts when company relationships matter.
Import Steps
- Open the relevant CRM import flow.
- Upload the CSV.
- Map CSV columns to Agiled fields.
- Review the mapping and required fields.
- Start the import.
- Check the import run for failed rows.
After the import finishes, open a few records from the list and confirm names, email addresses, account links, owners, stages, and custom fields were mapped correctly.
Use tags, created date, or import-specific values to identify imported records for review. This makes cleanup safer if a mapping issue appears after the run.
Import a small sample first when the file is new or the mapping is complex. Use records with normal values, missing optional values, custom fields, and relationship fields so you can catch mapping problems early.
For contact imports, include sample rows with an account name, owner, phone, email, status, tags, and custom fields. For deal imports, include the pipeline, stage, amount, owner, account, and contact relationship. This proves that the mapping handles the fields your team will actually rely on after import.
Fix Failed Rows
Failed rows usually come from missing required fields, invalid values, duplicate records, or formatting problems. Fix the source CSV and rerun only the corrected data.
Do not rerun the original full file unless you intentionally want to reprocess all rows. Use the failed-row export or a corrected small file so successful rows are not duplicated.
If many rows fail, stop and inspect the first few errors before changing the file. Repeated failures usually point to one mapping, required field, owner value, stage name, or relationship column that needs cleanup.
After Import Cleanup
Check duplicate records, missing owners, incorrect account links, wrong deal stages, and blank required custom fields. Run reports or saved views only after the imported data has been spot-checked.
Do not hand imported records to the team until the owner, status, and relationship fields are usable. Imported CRM data should be ready for follow-up, not just present in the database.
Create a temporary saved view or use an import tag to review the new records. Check a small set from the beginning, middle, and end of the file so formatting issues in later rows are not missed.
Bulk Cleanup After Import
Use bulk actions only after you have reviewed the imported records. Bulk edit is useful for assigning owners, applying tags, correcting statuses, or moving deals into the right stage, but it can also spread a bad value across many records.
Filter the imported records first, select only the rows that need the same change, then perform the bulk update. Open a few records afterward to confirm the change landed correctly.