IntegrationAdvancedoutbound-messagesplatform-eventsmigration
Migrate legacy Outbound Messages to Platform Events without downtime
Real World Scenario
Twelve production workflows send Outbound Messages to aging middleware; Salesforce roadmap deprecates OM and team needs zero-delivery-gap migration.
Expected Answer
• Parallel run: publish Platform Event from same workflow trigger while OM still active
• Middleware deduplicates dual delivery using record Id plus change timestamp
• Validate PE payload parity with OM fields before OM cutover per interface
• Replay Platform Event from earliest after middleware consumer upgrade
• Cutover per interface with rollback flag re-enabling OM 24 hours
• Retire workflow OM actions only after 7-day error-free PE delivery
• Document migration in integration catalog with owner sign-off
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Parallel run: publish Platform Event from same workflow trigger while OM still active Also consider: Middleware deduplicates dual delivery using record Id plus change timestamp In practice: Validate PE payload parity with OM fields before OM cutover per interface Optimize for scale and operational observability.
Architect Perspective
Outbound Message migration is cutover discipline—parallel run with dedup beats big-bang disable.