When an organisation switches Peppol provider, the SMP registrations need to be transferred. The Peppol migration protocol ensures this happens without downtime: senders can continue sending during the migration. The PSB offers two migration scenarios via the API.

If a party moves from eConnect to another Peppol Access Point provider, you prepare the migration via the prepareToMigrate endpoint:

GET /api/v1/peppol/{partyId}/prepareToMigrate

This endpoint does two things:

1. It marks the party in the eConnect SMP as "in migration"
2. It registers a migration key with the Peppol SML

The API returns the migration key in the response. Pass this key to the new provider, who needs it to take over the registration in their SMP.

{
  "migrationKey": "abc123-def456-ghi789"
}

After the migration, the party is automatically removed from the eConnect SMP.

If a party moves to eConnect from another Peppol Access Point provider, you need the migration key that the current provider has generated. Add this key to the party configuration via:

PUT /api/v1/peppol/config/party/{partyId}

With the migration object in the request body:

{
  "migration": {
    "key": "the-migration-key-from-the-current-provider"
  }
}

The PSB completes the migration automatically: the SMP registration is taken over and the SML is updated. From that point on, all Peppol messages for this party are routed through the eConnect Access Point.

If the migration key is invalid or expired, the migration fails and the API returns an error message. In that case, request a new key from the current provider.

1. The party decides to switch to another provider
2. Call GET /api/v1/peppol/{partyId}/prepareToMigrate
3. Pass the migration key to the new provider
4. The new provider takes over the SMP registration using the key
5. The registration at eConnect is automatically cleaned up

1. The party decides to switch to eConnect
2. The current provider generates a migration key
3. Call PUT /api/v1/peppol/config/party/{partyId} with the migration key
4. The PSB takes over the SMP registration and updates the SML
5. Then configure the desired capabilities and hooks

The Peppol migration protocol is designed for zero downtime. During the transfer, the party remains registered in the network. Senders who send an invoice at that moment will reach the party via the old or the new Access Point, depending on the timing of SML propagation. No messages are lost.

After a successful migration to eConnect, the party is reachable immediately, but SMP propagation across the Peppol network may take a few minutes. After the migration, always configure the capabilities and set up the required hooks.

Don't forget to set up user permissions and optionally a businessCard via the Enrollment API if that hasn't been done yet.

Need help with a migration? Contact TechSupport for guidance on the migration process.

• Peppol network via the API: SMP and capabilities
• Peppol registration via the API (Enrollment)
• Overview: the Procurement Service Bus (PSB)
• What is Peppol and how does the network work?
• Peppol international
• Register on Peppol (platform)
• E-invoicing with eConnect