A Latin American venture firm: Affinity → Attio notes migration

In one line. We scoped and delivered a notes migration for a Latin American venture firm moving from Affinity to Attio, carrying past pass reasons and company context across its Fundraising, Deals, and Talent lists.

Client & context

The firm was mid-move from Affinity to Attio. It had already migrated companies, people, deals, and one key list itself by CSV, and was running seven Affinity seats. A notice deadline to Affinity in late May set the timeline.

The problem

The remaining piece was notes, past pass reasons and company context, held across three lists: Fundraising, Deals, and Talent. These needed a dedicated migration path beyond the generic import. Affinity's API also carried usage limits that reset at the start of June, which shaped the migration timing.

What we built

• A scoped notes migration across the Fundraising, Deals, and Talent lists.
• A full-migration option covering contacts, organizations, notes, and lists, with a custom object if the notes needed one.

How we did it

We laid out two delivery paths: a manual CSV export of notes from each list into a custom object as a workable route, or a full API-based migration once Affinity's limits reset at the start of June, estimated at 24 hours to six business days of work. File attachments were scoped out. The plan depended on confirming post-notice archive access with Affinity and the API reset.

Outcome

The notes migration was delivered across the three lists, carrying the past pass reasons and company context that mattered to the team into Attio.

Takeaway: A notes migration delivered across three Affinity lists, Fundraising, Deals, and Talent, carrying past pass reasons and company context into Attio.