Service group record remains on source SMP after inbound migration via REST API #462

devZeynep · 2026-03-09T13:59:17Z

devZeynep
Mar 9, 2026

Hi,

when migrating a participant to a different phoss SMP instance via
PUT /migration/inbound, the SML/DNS entry is updated successfully but
the service group record on the source SMP remains untouched.

Since migrations can happen between different SMP providers, it is not
possible for the target SMP to automatically trigger finalization on the
source SMP.

What is the recommended approach here? Is there an existing mechanism or
any plans to handle cleanup of the source SMP record after a successful
inbound migration?

phax · 2026-03-09T16:34:31Z

phax
Mar 9, 2026
Maintainer

Hello @devZeynep
The Participant Migration process is a semi-automatic process.

The old SMP creates a Migration Token and marks the entry as "planned for migration"
The old SMP needs to communicate the token and the Participant ID manually to the new SMP
The new SMP imports the Migration Token from 1. and creates the Participant locally
The new SMP needs to communicate the success of the activity of step 3 so that it can manually delete the participant locally

Practically you need to use email or so.

hth and BR,
Philip

0 replies

Navigation Menu

Service group record remains on source SMP after inbound migration via REST API #462

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Service group record remains on source SMP after inbound migration via REST API #462

Uh oh!

devZeynep Mar 9, 2026

Replies: 1 comment

Uh oh!

phax Mar 9, 2026 Maintainer

devZeynep
Mar 9, 2026

phax
Mar 9, 2026
Maintainer