Bulk update records or lists via CSV import

Learn how to bulk update records and lists using CSV imports.

ON THIS PAGE

Learn how to use unique attributes to bulk update existing records and list entries via CSV import.

Summary of steps

  1. If you don’t already have a file with the records or list entries you want to update, start by creating a filtered view with the records you want to update, add any attributes you want in your file as columns in your table view or to your kanban cards, and export the view. If you already have a file, simply move to the next step.

  2. Ensure you have included a column with a unique attribute in your file so that Attio can match to and update existing records or list entries (rather than creating duplicates). Learn about unique attributes below. If importing into a list, find additional steps here.

  3. Follow the CSV import guide to import the file.

Include a unique attribute

To update existing records with a CSV import in Attio, you need to use a unique attribute that helps identify each record. Without a unique attribute, Attio will create duplicate records instead of updating existing ones.

What is a unique attribute?

Some attributes in Attio are designated as “unique”. When an attribute is unique, it means no two records can share the same value for that attribute.

For example, Domains and Email addresses are unique attributes:

  • Companies can have the same name but must have unique domains.

  • People can share names but must have unique email addresses.

Unique attributes for each object

  • Companies: Domains or Record ID

  • People: Email addresses or Record ID

  • Deals: Record ID

  • Users: Primary email address, User ID, or Record ID

  • Workspaces: Workspace ID or Record ID

  • Custom objects: Record ID, or admins can create custom unique attributes on custom objects

Note: It’s usually simpler to update records with a unique attribute like Email or Domain, rather than using Record ID.

However, you’ll need to use Record ID if there isn’t another unique attribute available or when you don’t have values for the other unique attributes (for example, if you need to update a company with an import but it has no domain). Learn more about using Record IDs below.

When to use Record ID and Entry ID

Record ID is a unique attribute on all objects, and Entry ID is unique on all list entries in Attio. You can’t add or change these IDs, and they are generated by Attio upon creation. But when all records or entries you want to import already exist in Attio, you can use the IDs assigned by Attio to locate and update the existing records.

Note: Do not include Record ID in your file if you’re adding any new records, as they won’t import successfully.

If you’re using Record ID to make updates and your file has a mix of existing and new records, split them into separate files, or use another unique attribute like Domains or Email addresses, which works for both existing and new records.

How to find Record IDs or Entry IDs

  • Record IDs are automatically included in any records or list export from Attio, under the column titled Record ID. Entry IDs are automatically included in any list export from Attio, under the column titled Entry ID.

  • Export a view including all the records you want to update to obtain a file with all the IDs.

  • Optionally, you can use a vlookup function in Excel to match record names to IDs if you have new data to add to your import.

Complete the import

Once you have ensured that your file has the necessary unique attribute included, follow the CSV importing guide to complete the import. Be sure to map the unique attribute on the Map columns step.

If a record with a matching unique attribute value is found in Attio, it will be updated with the new values from your file. If no match is found, a new record will be created using the information in your file (except when using Record ID, as explained above).

Below is an example of correct mappings for an import into a list of people. Entry ID, Record ID, and Email addresses are all unique attributes for People, so you would only need one of those. Mapping Company > Domains will also update which companies the people are connected to.

Note for importing more than one object

If your file contains data for more than one type of object, make sure to include a unique attribute for each object.

For example, if you are importing people and want to include their companies, include a unique attribute for People, such as Emails, and a unique attribute for Companies, such as Domains.

If you import People with just their companies’ names but no domains or Record IDs for the companies, you will create all new companies rather than connecting people to any existing companies.

Note for updating list entries

To update existing list entries instead of creating duplicates, make sure to:

  1. Include a unique attribute.

  2. Choose Update existing in the Map columns step of the import process.

Frequently asked questions.

  • If an object has multiple unique attributes and you need to update one of them, you’ll need to include Record ID in your import file to make the update. Here’s how:

    1. First, export your records from Attio to get the Record ID column.

    2. Add or update the other unique attribute’s values in your file.

    3. Re-import the file, ensuring you map the Record ID.

    For example, if you’re updating User IDs for users in Attio with an import, you’ll need Record ID in your file, as Primary email address (another unique attribute) can’t be used for this update.

Couldn’t find something? Contact us at [email protected]