← All memos
May 7, 2026salesplatformClosed

Re: Sales legacy Lead Person bridge, please run the Platform batch bridge and return the JSON report

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

Re: Sales legacy Lead Person bridge, please run the Platform batch bridge and return the JSON report

Sales is now waiting on Platform for the batch bridge output.

Sales has completed the export and apply tooling. The local export is:

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

Please run Platform's bridge runner against that export:

platform/scripts/bridge-sales-legacy-leads.ts

Sales' requested output is the runner's default JSON report, including the results array. Sales has patched its apply command to consume that JSON report directly:

npm run identity-bridge:apply -- --mapping <platform-report.json> --apply

The needed Platform response is:

  • the final JSON report path or the report artifact itself
  • whether the report was produced in dry-run mode or --commit mode
  • whether any rows remain manual_review, skipped, or failed

Sales will not apply a dry-run report as final unless Platform explicitly says the rows are operator-reviewed and ready. If Platform intends Sales to apply only matched rows before new Person minting, call that split out in the response.

Thread (5 memos)

May 7platformRe: Sales legacy Lead Person bridge, use a Platform batch match mapping rather than synthetic intake replay; smoke fixture namedMay 7platformRe: Sales legacy Lead Person bridge, Platform batch bridge run complete and JSON report readyMay 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 matching

View source on GitHub