CRM Sync
CRM sync is a managed Wander integration. Wander’s team configures, monitors, and operates it; your team maintains accurate source listings and agrees on field and category mappings with Wander.
Scheduled updates
Section titled “Scheduled updates”Wander regularly pulls published listings from your system. Your organization does not need to build a webhook or push changes to Wander. The time before an edit appears on the map depends on the managed sync schedule.
If you need one listing refreshed after correcting it, ask your Wander partner manager for an on-demand sync.
How listings are matched
Section titled “How listings are matched”For a previously linked listing, Wander first looks for an exact match on its stored external ID—the record ID from your system. This keeps the pairing stable when a name or address changes.
For a new or unlinked listing, Wander looks for a high-confidence name and address match among existing Wander places. A matching place is linked to the listing; otherwise, Wander creates a new place. After that first link, the stored external ID becomes the primary way to pair the records.
What syncs
Section titled “What syncs”Wander works with your team to configure which source fields map to Wander fields. These can include:
- Name and address
- Description and photos
- Categories
- Website and other listing details
Source categories are mapped into your map’s tag structure. Wander can also validate listing locations against your destination boundary so that out-of-area records can be handled appropriately.
Per-destination safety rules can protect selected Wander fields from updates. For example, a description curated by a Wander steward can remain unchanged even when the source listing has a different description. Your team and Wander should agree on field ownership during setup.
Removed listings
Section titled “Removed listings”When a listing disappears from your source system, Wander does not immediately remove the matching place. After consecutive absences, the listing is flagged as a delete candidate for review. This review helps prevent a temporary source issue from removing content from the map.
Store the Wander ID in your system
Section titled “Store the Wander ID in your system”Wander recommends adding a field such as Wander Maps ID to each source listing and storing the Wander place UUID there. This gives both teams a durable reference when reviewing records.
For Wild Apricot, Wander writes the ID back automatically. Read-only systems such as SimpleView do not allow Wander to write it back, so your team records it manually today. A manually recorded ID helps Wander’s team verify links; it is not currently used to create the link automatically.
Contact your Wander partner manager to plan mappings, review sync behavior, or request an on-demand sync for a listing.