Time consuming for sure, but this is the way I'd tackle what you're trying to do. If you're using persistent disks for users, I don't have a good answer and you should likely engage some migration help from professional services.
- Upgrade View to a version that supports the version of vCenter you're moving to
- Add the new vCenter to the View Instance
- Create a new Manual Pool
- Ensure you have at least one set of shared storage between the new and old vCenter Server
- Put some View VMs to be migrated on the shared storage between old and new vCenter Server
- Steps 6-11 are for each VM/user (Yes, downtime required)
- Remove from the View Admin Interface (do not delete)
- Remove from the old vCenter inventory
- Browse datastore and add to the new vCenter Inventory
- Add VM manually to the new manual pool
- Entitle the user to the new pool
Real world experience for me says if you have to do this with linked clones, you're better off building a new environment and simply copying over the golden images and updating them, since they'll likely require a tools update anyway. Then do a slight of hand switcheroo on migration day. I know this doesn't apply to your use case, but knowing can't hurt.
Update sequence for vSphere 5.5 and its compatible VMware products (2057795)