Serialize and deserialize will convert from a class to xml and back again.
However you end up very closely coupled. They change the service content....
Also at least in .Net 2 there's a bad memory leak in deserialise.
You have to do a lot of arsing about to get contained classes in.
Personally I'd do it the long way and put LoadFromXML and SaveToXML methods on a class perhaps in an interface , if you have several service responses or expect more or want some verion independance from the provider.
You could also use a class factory approach if the xml content gives you enough to identify which class to create.