Custom Fields not getting Migrated

[purvajainnn]

As discussed in the demo meeting, Veeva customers might have few other custom fields which might impact other workflows. We are running an analysis from our end, I will add more details on this issue for the same.

[nealmundy]

It is common for our customers to have created custom fields on the Territory object. A typical Use Case for doing so is to support downstream systems (typically Business Intelligence systems) that consume territory data.

If the migration tool does not support the migration of the data within these custom fields, then our customers will have to manually migrate this information themselves.

[VivekMChawla]

@nealmundy and @purvajainnn - I've confirmed that the Territory2 object supports custom fields, so adding this to the migration tool makes sense.

I'll mark this as a feature request.

[purvajainnn]

Thanks @VivekMChawla

[nealmundy]

Thanks @VivekMChawla