Sure, we have Content Deployment and STSADM export etc., but the lowest level of granularity is a web, and if you don't want to overwrite the whole thing neither option can be used.The only other option is to write code which uses the Content Migration API.
The text reader is used to walk through the nodes of the document whereas the validating reader examines and validates each single piece of XML according to the requested validation type.Although the Xml Validating Reader class inherits from the base class Xml Reader, it really implements internally only a very small set of all the required functionalities.This is fine for projects which have the appropriate development skills and time, but otherwise things can be tricky. The tool provides a wizard-like approach to deploying content between Share Point sites.The selected content is exported using the Content Migration API (PRIME), giving a file (Content Migration Package) which can be copied to other servers.On container objects such as webs, there are options about whether descendent objects should be included: And that's the gist of it.
This is the first beta of the tool and I'm sure there will be issues.
The schema exception class contains information about the line that originated the error, the source file and, if available, the schema object that generated the error.
The Severity field represents the severity of the event.
Each validation error found along the way results in an particular event being notified to the caller application.
Hence, to track messages and detects errors the application must define an ad-hoc event handler.
Regardless, when using any tool which makes this kind of change to your data you should always take a backup before performing the import.