Skip to main content

Legacy Migration CRM Notes → CDP — Status 2026-06-30

Delivery / Program Management — periodic status report. health: carries the delivery-health status (backlog / on-track / at-risk / off-track / paused / completed); the doc-lifecycle status: stays in the linter enum (active).

Summary​

At risk against the 2026-08-04 revenue commitment. The build plan is ready, but the migration is doubly blocked: by the cross-initiative P1 (Mention User in CDP Notes) dependency and by a net-new org-scoped extraction endpoint that the Legacy CRM Squad has not yet built. Both blockers are outside this initiative's direct control, exposing the deadline.

The 2026-08-04 date is not achievable by dependency alone — independent of the external endpoint. P4's hard prerequisite is P1 shipping (the contact_notes mention schema + parser must land first); the 2026-06-30 timeline-mapper run derives P1's own finish at p50 2026-08-05 / p85 2026-08-14. P1 therefore ships after P4's 08-04 commitment, so even with zero P4 build time and a ready CRM endpoint, the date cannot be met as long as P4 waits on P1. Honouring the P1→P4 dependency requires moving P4's date (or shipping P1 earlier via a scope-cut); no resequencing inside CDP resolves it.

Highlights​

  • RFC (2026-06-18) is Agentic-Ready, verdict PROCEED; pipeline, idempotency, sanitizer, resolver, rollback, and execution chunks are specified.
  • Build of chunks 1–10 can proceed now against a stubbed extraction interface.

Lowlights & blockers​

  • CRM extraction endpoint (🔴, run blocker) — owner: Legacy CRM Squad; ask: build a paginated org-scoped Person-notes extraction endpoint (HTML + creator_id + attachments + crm_note_type_id + timestamps). Does not exist today (Decision 10, OQ-7).
  • P1 dependency (🔴, cross-initiative) — owner: CDP; the migration cannot start until Mention User in CDP Notes ships (already tracked via depends_on).
  • Runtime gates (🟡) — per-CID coverage ≥99% (Data Eng, OQ-2); bulk-throughput load test (OQ-7); bluemonday/Infosec (OQ-10); CRM bucket access + PII residency (OQ-9); per-caller audit (OQ-11); CSM per-CID consent.

Risk & dependency changes​

  • New deadline-vs-dependency risk recorded: the 2026-08-04 commitment is gated on the P1 ship date and an uncommitted Legacy CRM Squad endpoint (dependency-check, 2026-06-30). Tracked on the roadmap ## External & cross-squad dependencies and this initiative's timeline.md ## Dependencies & gates. Health moved Backlog → At Risk.
  • Deadline-vs-dependency impossibility recorded (timeline-mapper, 2026-06-30): with P1's forecast finish at p50 2026-08-05 (p85 08-14) — after P4's 2026-08-04 date — the commitment is unachievable through the P1→P4 dependency alone, before the external endpoint is even considered. Decision required: move P4's date or cut P1 to a slice that ships its mention schema sooner.

Metrics​

Baseline reading (t0) — the dated sequence of these reports is the burnup trend.

  • Progress: 0 / TBD man-days (0%) — total pending DRI man-days.
  • Throughput this period: 0 (baseline).
  • Forecast: TBD (derived once effort is finalized and both blockers have dates).

Next period​

  • Secure a Legacy CRM Squad commitment + date for the extraction endpoint; track the P1 ship date; confirm per-discipline man-days so the TPM can test the 2026-08-04 date against the P1 → CRM endpoint → deploy critical path.