A venture capital firm: Affinity-to-Attio migration + intake automation

In one line. 80x took over an in-flight Affinity-to-Attio migration for a venture capital firm, built the records/notes/files pipeline to close a ~90k-to-2k record gap, organized 380 Drive folders, and built a Zapier intake form, and the client came back for a second project.

Client & context

A venture capital firm was migrating from Affinity to Attio. 80x took over a partly built migration from a previous engineer: a set of Python scripts on a standardized architecture, extract from source, normalize, load into Attio, with about 2,000 of ~90,000 records migrated so far.

The problem

The migration needed completing end to end: the records pipeline that everything else depended on, notes attached to the right company and person records, and file attachments handled through a separate Drive workflow. About 90,000 records in Affinity stood against roughly 2,000 in Attio, the gap 80x was brought in to close.

What we built

• The Affinity → Attio records, notes and files migration, closing the ~90k/2k gap.
• Organization of 380 folders from a shared Google Drive into person, company and deal categories.
• A Zapier intake form with LinkedIn-URL validation and DeckMatch deck-ID polling.
• Scripts uploaded to GitHub for review.

How we did it

The first step was an audit of the inherited code to decide between completing the multi-script pipeline or falling back to a CSV export/import. Drive folders were mapped to record types across person, company and deal categories. The intake form validated LinkedIn URLs with an HTTP-format check to handle blank or malformed entries, and polled DeckMatch for deck IDs. 80x also offered the option to run the migration script independently of Zapier to keep task usage low.

Outcome

The migration was completed into a working records/notes/files pipeline that closed the ~90k-to-2k gap, the 380 Drive folders were organized into person/company/deal categories, and the Zapier intake form was delivered. The client returned for a second project.

Takeaway: An in-flight migration with a ~90k-to-2k record gap was completed into a working pipeline, enough for the client to come back for a second engagement.