Import Contacts

Use imports when you already have contacts in a spreadsheet, another CRM, an exported customer list, or a legacy Agiled workspace.

Importing is faster than manual entry, but it can also create duplicates quickly. Clean the file before uploading.

Prepare the File

Use a CSV file with one contact per row. Keep column names clear so mapping is easy, such as first_name, last_name, email, phone, company, status, and tags.

Before importing:

• Remove duplicate rows where possible.
• Split full names into first and last name if your file has separate fields.
• Standardize status values to lead, prospect, customer, or inactive.
• Put multiple tags in a predictable format if your source app exported tags.
• Keep a backup copy of the original file.

Choose the Import Strategy

Use a small test import when the file is new, comes from another CRM, or includes custom fields. Ten rows are enough to confirm mapping, status values, tags, and account matching before importing the full list.

If the file contains existing customers, decide how duplicates should be handled before uploading. Email is usually the best unique identifier. If many rows are missing email addresses, add another cleanup step before importing so your team does not create several records for the same person.

Use tags to label the import source, such as webinar-may-2026 or legacy-crm-import. This gives you an easy review view after the import.

Import Contacts

1. Open CRM > Imports or the contacts import entry point.
2. Choose Contacts as the import type.
3. Upload the CSV file.
4. Map each file column to the correct Agiled contact field.
5. Review the preview and validation messages.
6. Start the import.

After the import runs, review the imported contacts from CRM > Contacts.

Map Fields Carefully

Map identity and communication fields first: name, email, and phone. Then map status, tags, account/company, assignees, and custom fields.

If a column does not belong in a standard Agiled field, create a custom field before importing or leave that column unmapped.

Run a small test import first when the file is large or includes custom fields.

Map Common Columns

Use this order while mapping:

1. Map first name, last name, and email.
2. Map phone and company or account.
3. Map status, owner, and tags.
4. Map address, website, source, and lifecycle fields.
5. Map custom fields only after standard fields are correct.

Leave a column unmapped when you are not sure where it belongs. It is better to rerun a clean import than to put spreadsheet notes into the wrong contact field.

After Importing

• Filter by status or tag to confirm contacts landed in the right segments.
• Spot-check several contact detail pages.
• Merge or clean duplicate records if your source data contained duplicates.
• Save a view for imported contacts if you need to review them later.

Open at least one imported contact and check the profile, account link, tags, custom fields, and activity timeline. If the contact should be used for deals, invoices, projects, or chat, confirm the record has enough information for those teams before you mark the import complete.

Clean Up an Import

Create a saved view for the import tag or import date. Use that view to:

• assign owners
• add missing statuses
• bulk update tags
• review contacts without email addresses
• identify duplicates
• export a backup of the imported segment when needed

Troubleshooting

If contacts import without expected values, review the mapping and source column names before running another import.

If duplicates appear, stop importing and clean the source file or use saved views to review the imported batch.

Related Docs

• Contacts
• Contact Filters and Views
• Contact Custom Fields
• Imports Settings