Forum Discussion
Gereal question about structure and virtual servers!
Hi,
At my workplace there is an idea about migrate from SharePoint server 2010 to 2013 or 2016 (on prem). For that, people has been looking for migration options and they are very interested in ShareGate. In order to have a good idea about how the process goes I have read a lot of documentation about migration but I don't have any test environment.
I was thinking in setup an environment with Hyper-V. My plan is to have two single server farm SharePoint machines, one for 2010 and another 2013 or 2016. In the 2010 virtual machine I will create a lot of site collections, libraries and lists some custom web parts. I will not create any custom design since as I understand there will be problem with that during the migration.
Now, I will install a trial ShareGate to test the migration my question is: where to install it? in the 2010 virtual machine? in the 2013?
Another question is how should I configure the VM ip numbers so the 2010 vm can see the 2013 vm (or 2016 vm)? I suposse that if I install ShareGate in the 2010 vm, this vm should be available to see the 2013 vm in order to connect via the application and make the migration.
Or is possible to setup the virtual machines in some way so both are accesible from the host OS?
Best resgards
Americo
2 Replies
- If you are going to use Sharegate for the migration, you can make a direct migration...also since Sharegate uses Client Side Object Model to do the migration, you could potentially install when you want but in this scenario I would probably install it in the SP 2010 environment
- Americo PerezIron Contributor
Thanks Juan Carlos,
I am installing right now SP2010 in a virtual machine and I will follow your recommendation and install ShareGate in the same machine.
Once I am finish with the other vm (2013) I will make a test and I post the results.
Regards
Americo