Question 1

Do I need Attio record IDs in my data warehouse?

Accepted Answer

No, and that is what makes this practical. Identity can be an email address on people, a domain on companies, or any suitably unique attribute you already hold, including a custom attribute carrying your own account identifier. Companies and people get dedicated domain and email handling for exactly this reason. Where a source column holds several values, each is checked in turn until one matches. Matching on a non unique attribute works but will update every record it matches, so it is worth confirming uniqueness first.

Question 2

Where can modelled data land in Attio?

Accepted Answer

Any object your workspace exposes as writable, which includes custom objects, since objects are discovered live rather than read from a fixed list. Lists are writable too, so a segment can be pushed into a named list with its entry attributes set in the same sync. Some things are readable but not writable: notes, meetings, call recordings, workspace members and the derived deal stage history. Write modes are create, update, and create or update. There is no delete.

Question 3

How are relationships and select fields handled?

Accepted Answer

Relationships can be set by pointing at a unique field on the related record rather than needing its Attio identifier, so a person can be attached to their company by domain. Where a column holds several company identifiers, the record is associated with every valid one. Multiselect attributes merge with what is already there by default, with a setting to treat your values as replacements instead, and new select options can be created automatically rather than being maintained by hand.

Question 4

What happens on a large first load?

Accepted Answer

It paces itself rather than failing. Attio allows a lower rate for writes than for reads, and Polytomic deliberately throttles below that ceiling, working through records in batches. Rate limited and transient requests retry with backoff, so a large backfill queues and completes over time instead of erroring out. After that first load, model syncs are differential, so later runs carry only what changed and stay small even when the underlying Snowflake table is large.

Question 5

How do I connect Snowflake to Attio?

Accepted Answer

Connect Snowflake with account details, a role, a warehouse and credentials, and connect Attio with OAuth, granting access to the objects you want to sync. Objects are then discovered from your workspace, so custom objects and lists appear without extra configuration. Model the data in Snowflake with one row per record, choose the object or list to write to, and map an identity such as email or domain so existing records are matched rather than duplicated.

Connect Snowflake with Attio

Connect Snowflake and Attio with Polytomic

Matched on email or domain

Custom objects and lists

Relationships by lookup

Trusted by businesses worldwide

Step-by-step integration guide

Connect Snowflake in Polytomic

Connect Attio in Polytomic

Create a sync between Snowflake and Attio

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Snowflake with Attio?