Mapping Custom Objects

Learn about mapping custom objects in Switch.

Custom objects can be mapped to existing default objects in the destination CRM platform.

In case a corresponding default object does not exist in the destination CRM platform, you need to create a custom object to map it.

Scenario 1: A custom object ABC exists in your source CRM which does not have any corresponding custom object or default object in your destination CRM platform. Create a custom object to map it in your destination.

Scenario 2: A custom object DEF exists in your source CRM which already has a corresponding custom object created in your destination CRM platform. Select that custom object from the drop-down menu to map it.

Scenario 3: A custom object GHI exists in your source CRM which you want to map to a default object in your destination CRM. Select that default object from the drop-down menu to map it; provided it hasn’t been mapped to another object.

Mapping two objects to a single object is not permitted to prevent data inaccuracies. In case you map a single object to two different objects, an error message will appear to rectify the same.

Object mapping can vary depending on the platforms. Some platforms do not support custom objects, and thus cannot be mapped. Reach out to us to find the best solution.