Mapsly is a standalone geo-intelligence platform that extends capabilities of your CRM or any other data source with features related to geo-analysis, routing planning, territory management and lead generation.

Multiple data sources

Mapsly supports any number of data sources. For widely used cloud CRMs the Mapsly team developed connectors, while for more rare or proprietor data sources it's possible to develop a connector in within a day. (Contact us to receive documentation and guidance for building custom Mapsly connectors.)

Mapsly works with any data structure and any volumes of data

Mapsly is entirely metadata-driven: it reads the data structure of your CRM instance and builds a native database to store your data in its native data types, and keeps the structure in sync with your data source by following changes to the structure that you make in your CRM (i.e. by automatically adding and removing fields). This enables Mapsly to offer all of its features not only to standard CRM objects like leads, accounts and contacts, but to any custom objects and fields, without sacrificing performance: Mapsly easily handles tens of millions of records in a customer's database and tens of thousands points on the map at a time.

The stored information about the types of your data fields ("metadata") allows Mapsly to not only offer appropriate types of filters in the interface, but also understand the relationships between your objects such as lookups and multi-select lookups.

Smart data sync

For performance purposes, Mapsly imports your data to its database and then occasionally (by default, once per 30 minutes) import new and update records for all the currently enabled objects, as well as delete records that is deleted in the data sources as well as converted leads.

Data modification capabilities enabled by metadata

Using the metadata, Mapsly allows users to update their CRM data right in Mapsly, one record at a time, or thousands records at once. It also allows assignment of values to lookup fields (the object being referenced by the lookup field is not required to be added to Mapsly) as well as multi-select lookups (Mapsly can create and delete records from the linking tables thus adding or removing lookup values in the multi-select lookup fields).

Did this answer your question?