Use cases — batch mep cep five api field map

Two concrete scenarios for the 2026-12-31 migration window. Local-only helper.

Mobile CRM integrator: Produce a five-API migration map for engineering before Dec 31

Steps: Select APIs in scope → generate map → add auth notes → assign owners → export

Result: Markdown map covering CEP targets and In-App console path

Role context: mobile-crm-integrator in batch-mep-eol-dec31. Deadline 2026-12-31. Vehicle field-map. Keep the export attached to the ticket and re-verify official sources.

Backend messaging owner: Replace webhook export integrations ahead of EOL

Steps: Flag Webhooks MEP → map to CEP Export → update auth → contract test → cutover

Result: Webhooks MEP callers removed; Export API live with project header

Role context: mobile-crm-integrator in batch-mep-eol-dec31. Deadline 2026-12-31. Vehicle field-map. Keep the export attached to the ticket and re-verify official sources.

Next: home tool · how-to · FAQ.

Treat In-App separately in program plans: product owns Orchestrations rebuilds while engineering owns Campaigns, Audiences, Catalogs, and Export API callers. Rotate CEP tokens and project headers in lockstep with endpoint swaps so half-migrated clients do not flap. Keep Transactional and GDPR out of the December 31 panic list unless product explicitly expands scope. Export the field map into the migration epic with links to the MEP status table and the CEP readiness guide. This map never calls Batch.