·To Replicator, web parts are just discrete pieces of a page. We don't need to know anything about them beyond the configurable properties users can specify for them. When we replicate a page, we get a list of parts on the page and then ask SharePoint for all of the properties associated with each web part. Replicator then packages (serializes) everything we know about the part and transfers it to the other sites. We do not replicate the parts themselves, only their properties. When we get to the target, we add the part to the page and apply all of the properties to the web part on the replicated page. This is why we require web parts be installed and available in all locations before we replicate pages that contain them.
·With regards to web parts that use complex data structures for their properties or have properties that are not serializable, Replicator cannot package them. We don't know the specifics of any property data structures and rely on the properties being serializable for the packaging, as serializable properties in a program ensure the properties can be copied exactly.ss
·If you have the ProcessUnSupportedWebParts configuration flag set to true, then Replicator will process all web parts as being supported. That is, web parts will be packaged on the source web application and cleared from the page on the target web application before re-adding them all to the page on the target web application.
·You should always ensure that you have properly tested the replication of any custom web parts in a non-production environment before installing them into the production environment and enabling the ProcessUnSupportedWebParts configuration setting.