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.
Migrating from Geoapify
Geoapify bundles geocoding alongside routing, places, and map styling APIs under a single apiKey parameter, which suits teams that want one account managing several location features at once. Its geocoding responses follow a GeoJSON-like structure with a features array, each carrying properties for address fields and geometry for coordinates.
Because Geoapify covers more than geocoding, a migration away from it is rarely all-or-nothing. It is worth being deliberate about scope: are you moving every location feature at once, or just the geocoding calls while leaving routing or map styling on Geoapify for now. Both are reasonable, but they lead to different amounts of work, and mixing them up midway through a project tends to cause confusion about which key is authenticating which request.
My Geocode is a geocoding, IP, timezone, elevation, and postal code lookup API, so it is a direct replacement for the geocoding portion of a Geoapify integration specifically. The Geoapify compatibility host reproduces the features array and its nested properties and geometry fields, changing only the copyright, terms, and privacy text in the response. Field details are at /compatibility/geoapify/.
For the geocoding calls, moving means:
- Pointing the request at the new host instead of Geoapify's
- Sending a My Geocode key instead of the Geoapify
apiKey, in whichever of the four supported styles your client already uses (X-API-Key,Authorization: Bearer, HTTP Basic auth, or query parameter) - Leaving the code that reads
features[0].propertiesandfeatures[0].geometry.coordinatesuntouched
If routing or places lookups are staying on Geoapify for now, nothing about that changes; the geocoding compatibility host operates independently and does not require the rest of your stack to move at the same time.
Pricing is where a bundled account and an unbundled one diverge in structure rather than just in number. My Geocode charges the same rate for every endpoint, including every compatibility host: 2,500 free requests a day with no key, 2,500 more free per key per day counted per network, then prepaid credit at €0.0001 per request or an Unlimited key at €50 a month. There is no separate pricing tier for geocoding versus other lookups, which simplifies the math if you decide later to move more of a Geoapify-based stack over.
Optional extras, ground elevation, IP threat detail, and network information, are available on the geocoding compatibility host by adding mg_extras=1 or an X-MG-Extras header, which is worth knowing if part of the reason you used a bundled provider was to get more than one kind of data back from a single call.
Migrating one piece of a multi-feature account is a normal, incremental way to reduce dependency on any single vendor, and it does not require a firm decision about the rest of the stack on day one.