Migrate from eSIM Go to Bird

Move the bundle ordering and assignment flow while retaining the records for already-issued eSIMs. eSIM Go distinguishes catalogue bundles, order validation, purchase and bundle assignment; rebuild those responsibilities explicitly around Bird offers and orders.

Follow the Bird purchase and installation guide with a test customer and device. Verify the order, private installation and working service before changing fulfillment routing.

Record the catalogue bundle, order reference, customer and ICCID for each active service. Also inventory purchased bundles that have not yet been assigned. Retaining only the storefront product name loses information needed to reconcile orders and support existing customers.

The eSIM Go quickstart describes validate and transaction request types. Those are supplier operations, not Bird request fields. Likewise, importing an order reference does not transfer a purchased bundle or an installed profile.

The v2.5 order reference distinguishes these inputs:

The supplier's compatibility endpoint answers whether a specific ICCID and bundle work together. For Bird, start with Top up on the receiving profile. Check the eSIM named in Confirm top-up before approving the displayed plan and price.

Keep the selected Bird plan and displayed price with the customer's purchase record. If the browser closes before showing the result, find the original order in Orders or the eSIM's Purchase history before buying again.

Account for unassigned supplier inventory independently from new Bird purchases. Preserve the original usage and assignment records for existing eSIM Go services until they are no longer needed for fulfillment or support.

Follow the Bird integration and installation guides on a device you control. Keep the order reference through funding and provisioning, then verify actual mobile data on a covered network.

Include an unassigned inventory purchase, an existing-profile top-up and a new-profile purchase in the migration checklist. Confirm an incompatible top-up remains a refusal until the customer chooses another service. Interrupt a purchase response and verify recovery preserves the original Bird order. Reconcile the old supplier's inventory and each delivered package before changing fulfillment routing.

Keep existing eSIM Go profiles supported until their service ends or the customer chooses a new installation. A Bird top-up must be eligible for the receiving Bird eSIM; it is not a way to add data to an unrelated supplier profile.

Route a bounded set of new purchases to Bird. Verify pricing, installation delivery and support records. Reconcile uncertain orders before retrying; restoring old storefront routing does not undo a fulfilled purchase.