I have a large document library with a number of custom columns that must be maintained while migrating from an on-premise 2010 environment to SharePoint O365.
Here are the scenarios I've explored:
- Server side code - 2010 Server-Side Object Model code will not run in the 4.0 framework, so I don't think it's going to be possible to simultaneously house both sets of code to export the items from 2010 and import the items into 2013 within a single Visual Studio project. Any suggestions on how to get around this?
- Powershell - O365 does not appear to have any command-lets available to import at the site level or list level. (https://technet.microsoft.com/EN-US/library/fp161388.aspx)
- Client side code - I don't have a lot of experience with the 2010 JSON libraries, but I'm guessing I can use straight JavaScript and/or web services to export from 2010 and then import to O365 2013? I know the client-side libraries available
within 2010 were minimal, so I'm not certain this is a feasible scenario.
I really thought this would be simpler than it has turned out to be, and I'm considering exploring 3rd party tools at this point. Additional thoughts/suggestions? Thanks in advance! :-)