Migrating a Zapier or Make automation to a new geocoding host
No-code automations built on a geocoding step need a different migration approach than custom code does. Here is how to handle that switch.
Tag
#migration
Why migration should take an afternoon, not a quarter
If switching a location API takes a quarter, the previous integration was designed to make leaving expensive, whether or not that was the stated intention.
Migrating a server-side integration without touching the client
A server-side geocoding migration can often be invisible to the client applications that depend on it. Here is how to design it that way.
Migrating a mobile app's geocoding calls
Geocoding calls from a mobile app carry constraints a server-side migration does not have to think about. Here is what to plan for specifically.
Coupon codes for teams moving from a competitor
Coupon codes are now available in the dashboard, giving teams switching from another provider an extra reason to make the move now.
Migration guides: a new home for switching providers
Dedicated migration guides now walk through switching an existing integration to My Geocode, provider by provider, endpoint by endpoint.
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 public compatibility matrix: seventeen hosts, one key
A single page now lists all seventeen compatibility hosts side by side, making it easy to see which providers can be swapped in with one key.
Self-hosting Open-Elevation vs using a managed endpoint
Open-Elevation can run on your own infrastructure or against a managed endpoint. Here is what each path actually costs in effort and money.
Moving off Mapbox static maps and tiles for geocoding-only use
A lot of Mapbox integrations bundle geocoding with map rendering. Here is how to separate the two and migrate only what needs to move.
Moving off a HERE autosuggest integration
HERE's autosuggest has its own request pattern distinct from geocoding. Here is what to think through before moving it to a new provider.
Moving off a Bing Maps elevation integration
Bing's elevation data ties into its broader Maps account. Here is how to extract and migrate just that dependency.
Moving off a Bing Maps time zone integration
Bing's time zone data is often tied to the same account as its geocoding calls. Here is how to separate and migrate that one piece.
Moving off a Google Places autocomplete integration
Autocomplete is one of the trickier pieces to migrate because its request pattern and session behavior differ across providers. Here is what to plan for.
Drop-in compatibility with Geocode.Farm is live
Geocode.Farm requests now work against our host unchanged, matching its parameters and response fields with only a host name and key to update.
Moving off a Google Maps Platform elevation integration
Elevation lookups are usually a small dependency inside a bigger Google Maps account. Here is how to move that specific piece cleanly.
Drop-in compatibility with Open-Elevation is live
Open-Elevation requests now resolve against our host, returning elevation figures in the same shape, switchable with only a host name and key.
Moving off a Google Maps Platform time zone integration
A Google time zone lookup is often bundled with a bigger Maps Platform account. Here is how to move just that piece.
Drop-in compatibility with OpenStreetMap Nominatim is live
Requests built for OpenStreetMap Nominatim now work against our host, matching its parameters and response shape with only a host and key changed.
Migrating from ipstack
ipstack's nested connection object and access_key parameter are common patterns to preserve during a migration. Here is how that works.
Drop-in compatibility with PositionStack is live
PositionStack-shaped requests now resolve against our compatible host with matching fields, so an integration can switch with only a host name and key.
Migrating from ipinfo.io
ipinfo.io's compact loc and org fields shaped a lot of downstream code. Here is what a migration to a compatible drop-in host preserves.
Drop-in compatibility with Geocodio is live
A compatibility host for Geocodio now reproduces its request and response format exactly, so an existing integration only needs a new host and key.
Migrating from ip-api.com
ip-api.com's flat JSON response is widely copied elsewhere in the industry. Here is what changes when you migrate that specific integration.
Drop-in compatibility with MapQuest Geocoding is live
MapQuest Geocoding requests now work against our host unchanged, matching its parameters and response fields so switching needs only a host and key.
Migrating from Geocode.Farm
Geocode.Farm serves a smaller niche in the geocoding market. Here is what a migration to a compatible drop-in host actually involves.
Drop-in compatibility with TomTom Search is live
A compatibility host for TomTom Search now reproduces its request and response format exactly, letting existing integrations switch with a host and key.
Migrating from Open-Elevation
Open-Elevation is a self-hosted, open source elevation API with a simple request shape. Here is what moving to a managed endpoint changes.
Drop-in compatibility with Geoapify is live
Geoapify-shaped requests now work against our compatible host with matching parameters and response fields, needing only a new host name and key to switch.
Migrating from OpenStreetMap Nominatim
Nominatim's usage policy and self-hosting realities push a lot of teams toward a hosted equivalent. Here is what that move looks like.
Drop-in compatibility with LocationIQ is live
Requests written for LocationIQ now resolve against our compatible host, matching parameters and response fields exactly, switchable with a host and key.
The quiet cost of vendor lock-in
Lock-in rarely shows up as a single bad decision. It shows up as a hundred small ones that quietly make leaving cost far more than simply staying put.
Migrating from PositionStack
PositionStack keeps its API deliberately simple. Here is what a migration to a compatible drop-in host preserves and what it changes.
Drop-in compatibility with OpenCage is live
A compatibility host for OpenCage is now available, matching its request parameters and response shape so existing integrations need only a new host and key.
Migrating from Geocodio
Geocodio is known for US and Canada address depth and bulk CSV geocoding. Here is what to expect when moving that workflow elsewhere.
Drop-in compatibility with ipstack is live
An ipstack integration now works against our host without changes to its request or response handling, aside from a new host and key.
Migrating from MapQuest Geocoding
MapQuest Geocoding has a long history in consumer mapping. Here is what a migration to a compatible drop-in host actually requires.
Drop-in compatibility with ip-api.com is live
Calls built for ip-api.com now resolve against our host with matching fields, so switching needs nothing more than a new host and key.
Migrating from TomTom Search
TomTom Search sits deep in automotive and fleet software. This post covers what changes and what stays fixed when you move the geocoding piece.
Drop-in compatibility with ipinfo.io is live
An IP lookup built for ipinfo.io now works against our host with the same fields coming back, switchable with a host name and a key.
Migrating from Geoapify
Geoapify bundles several location APIs behind one key. Here is what a migration of the geocoding piece specifically involves.
Drop-in compatibility with Mapbox Geocoding is live
Existing Mapbox Geocoding requests now work against our compatible host unchanged, matching its parameters and response shape exactly, minus the branding.
Migrating from LocationIQ
LocationIQ built its offering on open geographic data with a straightforward key-based API. Here is what changes when you migrate away from it.
Drop-in compatibility with HERE Geocoding and Search is live
A new compatibility host reproduces HERE Geocoding and Search requests and responses exactly, so switching over needs only a host name and a key.
Migrating from OpenCage
OpenCage built its name on simple onboarding and blended open data. Here is what a migration to a compatible drop-in host looks like in practice.
Drop-in compatibility with Bing Maps REST Services is live
Requests built for Bing Maps REST Services now work against our host unchanged, matching the same parameters and response fields exactly.
Migrating from Mapbox Geocoding
Mapbox Geocoding returns GeoJSON, which shapes a lot of downstream code. Here is what changes and what does not when you switch providers.
Drop-in compatibility with Google Maps Platform is live
Point your existing Google Maps Platform geocoding calls at our host with a new key, and the request and response shape stays exactly the same.
Why compatibility hosts matter more than a new SDK
An SDK asks you to trust one company's client library for the life of your project. A compatibility host asks you to change one line of configuration.
Migrating from HERE Geocoding and Search
HERE's Geocoding and Search API is common in automotive and enterprise stacks. This post covers what a migration to a drop-in host involves.
Migrating from Bing Maps REST Services
Bing Maps REST Services integrations lean on a distinctive resourceSets structure. Here is what a migration to a drop-in host actually touches.
Migrating from Google Maps Platform: what changes, what stays
A look at what actually changes when you point a Google Maps Platform integration at My Geocode, and what your existing code gets to keep untouched.