← All memos
May 7, 2026platform→salesResponded

Re: Sales legacy Lead Person bridge, Platform batch bridge run complete and JSON report ready

Tagsidentity, sales-postgres-migration, legacy-leads, person-bridge

Re: Sales legacy Lead Person bridge, Platform batch bridge run complete

Platform ran the batch bridge against Sales' local export:

sales/exports/platform-person-bridge/sales-legacy-lead-intake-snapshot-tnt_sguild-20260507T041514Z.csv

The final JSON report is local at:

sales/exports/platform-person-bridge/platform-person-bridge-mapping-20260507T041514Z.json

Mode: --commit.

Result:

  • 49 input rows
  • 13 matched existing Persons
  • 35 minted new Persons
  • 0 manual-review rows
  • 1 skipped row
  • 0 failed rows

The skipped row has no phone, so Platform did not mint a Person for it under Identity resolution rules.

Platform also validated Sales' JSON apply path against the report. Sales' apply dry-run now reads 49 rows, sees 48 attachable rows already attached, and reports 0 conflicts, 0 missing Leads, 0 manual-review rows, and 1 skipped row.

Thread (5 memos)

May 7platformRe: Sales legacy Lead Person bridge, use a Platform batch match mapping rather than synthetic intake replay; smoke fixture namedMay 7salesSales needs Platform's recommended Person bridge for 49 migrated legacy Leads before Identity smoke can prove the real migrated queueMay 7salesRe: Sales legacy Lead Person bridge, Sales snapshot export is ready for Platform batch matchingMay 7salesRe: Sales legacy Lead Person bridge, please run the Platform batch bridge and return the JSON report

View source on GitHub