1) There will be some work involved, yes. Many of the concepts are the same, but you have to get your head around the fact that your entities, and the loading and saving of them are now seperated.
2) Adapter templates still contain custom code regions, but I don't think that they would be preservered if you switched from generating a self-servicing project to adapter - you may need to manually copy them over.
3) GetMulti is not used at all in Adapter - the nearest equivalent is the FetchEntityCollection method of the DataAccessAdapter. Connection strings can be passed to the DataAccessAdapter constructor on initialisation and are then used for the lifetime of the DataAccessAdapter instance.
FWIW I ALWAYS use Adapter myself in the projects that I do. I feel the seperation of the entities from the persistence logic makes it much easier and cleaner to build properly layered applications.
Matt