Roster-to-cluster migration: a hands-on guide

A hands-on guide for brand and agency teams migrating from a hand-curated influencer roster (typically a spreadsheet) onto a cluster-based Creator Commerce OS without throwing away the institutional knowledge already embedded in the roster.

What's inside

• CSV / API import shape — the columns that matter for migration: handle, platform, past relationship, payment history, brief history.
• Scoring overlay — how cluster scores get applied to your imported roster and what the three resulting buckets look like (agree, roster-high cluster-low, missing).
• Triage workflow — how to review each bucket and decide who moves into auto-invite, who needs investigation, who gets onboarded.
• Operating cadence — weekly and monthly rituals that keep the roster and cluster signal in sync.
• Retiring the spreadsheet — when and how to deprecate the old roster doc.

Who this is for

Brand ops leads, agency operators, and creator-program managers running between 50–500 creator relationships on a spreadsheet today, who want to move onto a platform without losing the historical context.

What this isn't

• A pitch for any one platform. The mechanics described work on any cluster-based Creator Commerce OS.
• A throw-it-away-and-start-fresh manifesto. The historical roster carries genuine value; the migration preserves it.

Why migration matters more than rebuild

Six months of operating on a cluster engine gives you compounding signal: each campaign sharpens the cluster, each cohort sharpens the targeting, each brief gets easier to ship. Six more months on a spreadsheet gives you a slightly longer spreadsheet. The cost of not migrating is opportunity cost, paid quietly, for several quarters.