Migrate from 1GLOBAL to Bird
Move the selected connectivity service while preserving the subscription and customer support responsibilities around it. 1GLOBAL Connect covers ordering, activation and subscription management, so inventory the service lifecycle as well as the eSIM installation.
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.
1. Identify the interface and service in use
Record the Connect API version used by your integration, the customer record, active plans, installed profiles and ongoing subscription actions. The current documentation and legacy Connect interface have separate entry points; use the contract your application actually calls when mapping requests and events.
| Existing responsibility | Receiving decision |
|---|---|
| Customer and subscription record | Keep the application customer as the owner and associate new Bird order and eSIM IDs with it. |
| Plan selection and renewal | Check whether the chosen Bird offer is a new service or additional data, and implement that lifecycle explicitly. |
| Activation and installation | Follow funding and provisioning before exposing the supported installation method. |
| Ongoing service and support | Preserve the original supplier reference for existing plans and route each support action to the service that owns it. |
The Connect V3 new-eSIM recipe establishes an account and subscriber, selects a product offering and then starts subscription activation. Map those responsibilities before translating a request:
| Connect V3 responsibility | Bird receiving implementation |
|---|---|
| Account and subscriber | Retain the customer in your application and authorize access to its Bird order and eSIM. |
| Product offering | Select the Bird plan by displayed coverage, included services, allowance and validity. Record the accepted price. |
| Activation order | Create a Bird eSIM order and store its ID; preserve the original customer and supplier references. |
| subscription.sim_profile.ready_for_installation | Read the receiving order/profile and retrieve authorized installation credentials when available. |
| order.completed or order.failed | Observe the Bird order's actual status; completion, installation and first network use remain separate checks. |
1GLOBAL's retry contract uses Idempotent-Replayed and Idempotent-Retriable. Keep those rules with the source integration. During the Bird evaluation, recover an interrupted purchase by locating its existing order, as described in operations, before starting another purchase.
2. Choose a complete replacement service
Compare the required data, mobile voice or SMS service, coverage, number requirements and plan lifecycle separately. A successful data connection does not establish parity for every service in a mobile plan.
Record the chosen Bird plan and displayed price with the purchase. Test renewal or additional-data behavior if your product promises it, and document how customers with an existing 1GLOBAL installation continue receiving support during the transition.
3. Test one purchase and installation
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.
Test a new customer and an existing subscriber separately. Confirm the customer record stays intact, the new purchase has its own Bird identities and the old service remains supportable. Test changed pricing, pending provisioning, a failed order and an interrupted response.
Review 1GLOBAL's installation recipe if the application installs profiles or manages APNs through Android carrier privileges. That setup is tied to the supplier profile and application configuration. Revalidate the receiving device path instead of assuming permissions or installation links transfer with the account. Follow the returned Bird credentials and instructions for the new profile.
4. Handle top-ups and existing customers
Keep existing 1GLOBAL 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.
5. Move the storefront gradually
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.
References and next steps
- Device and coverage checks
- eSIM pricing
- Order flow
- Installation
- Usage and top-ups
- 1GLOBAL documentation
- Compare Bird and 1GLOBAL
- All migration guides
- eSIM resources
Verwandte Ressourcen
Weiter mit der Dokumentation, Anleitungen und Beispielen zu diesem Thema. Die Ressourcen sind auf Englisch.
Das Konzept verstehenWhat is an eSIM?Die Funktion erkundeneSIMImplementierungsleitfadeneSIM connectivity guide
Implementierungs-Briefing erhalten