Updating client libraries and SDKs during a migration
A migration is not just a backend change if your application relies on a provider's official client library. Here is how to handle that layer.
Blog topic
Migration (page 2)
Moving from Google Maps, Bing Maps, Mapbox, ipinfo, ip-api and others: what changes, what stays, and how to test the switch.
Re-mapping cached results after a provider switch
Cached geocoding results from an old provider do not automatically translate to a new one. Here is how to handle that cache correctly during a migration.
What a provider's notice period means for your migration
A shutdown or deprecation notice sets your migration's real deadline. Here is how to use that notice period well instead of losing it to indecision.
Comparing batch and bulk support across providers
Bulk geocoding needs are handled differently across providers, from CSV uploads to batch API calls. Here is how the common approaches compare.
A zero-downtime checklist for changing your API host
Switching a live API host without an outage takes more than just updating a URL. Here is a checklist for doing it without users noticing.
Estimating your real quota needs before you switch
Guessing at request volume before a migration leads to either overpaying or hitting limits unexpectedly. Here is how to estimate it properly.
Planning a rollback before you migrate anything
A migration plan without a rollback plan is only half finished. Here is what a real rollback plan for a location data provider switch looks like.
Mapping error codes between providers before you switch
Error handling code is often the most overlooked part of a provider migration. Here is how to map error codes properly before cutting over.
A checklist for running two providers side by side
Running two geocoding providers at once, even temporarily, requires a bit of deliberate structure. Here is a practical checklist for doing it well.
What relying on a single small provider teaches about vendor risk
Depending on one small provider for location data works fine until it does not. Here is what that risk actually looks like and how to reduce it.
Only Migration, as it is published.
Subscribe to Migration