Hi
Is it possible to migrate documents and apply metadata to the documents that have been created with Microsoft 365 Document Integration, these documents are already stored in SharePoint.
Documents that have never been stored in SoArc Online. Some customers have used Microsoft 365 Document Integration since they started using SuperOffice.
We have done some test with a demo tenant that used to be configured with Microsoft 365 Document Integration and we enabled SharePoint documents 2.x. And used the migration tool to move documents. It worked to move documents, and as far as we can see, metadata have been applied.
Is our testing correct?
In some cases a customer might have Microsoft 365 Document Integration and documents stored in SoArc Online (signed documents). Is there a solution here?
To move everything to SharePoint documents 2.x
At some point DataBridge can perhaps be useful here, but at the moment you cannot import documents, when SharePoint documents 2.x is in use.
All Replies (0)
The idea is that it is the same to migrate documents from so_arc (online) and from SharePoint 1.0 --> SharePoint 2.0
- our tests show that it works fine - and based on your feedback it did for you too.
Now we are ready to get some pilots on - so we get to test more in practice as well.
NOTE "migrate documents --> SharePoint 2.0" requires that you have configured SharePoint 2.0 first.
if you use so_arc (online), or SharePoint 1.0 - you should be able to configure SharePoint 2.0 from Admin - as long as the pre-req is in place (IDP auth)
How to migrate from version 1.0 to 2.0?
- in principle there should be no difference if you use so_arc (online) or SharePoint 1.0 for:
a) configure SharePoint 2.0
b) migrate existing documents to 2.0
For SharePoint 1.0 customers:
c) inform Support (-> SO R&D): 'turn off SharePoint 1.0 for customer XXXX'. (this will remove/turn off the old legacy login process "SuperOffice Integrator App in Microsoft 365 SharePoint" -> normal SuperID login process)
a) is documented on docs
b) is documented on the pilot forum
signed documents / DataBridge / other 3.party document-integrations - Is there a solution here?
- for most of the feedback we have seen so far - it has been due to not configured in the setup of "Apps for SuperOffice (system user)"
Enable system user for storing documents in SharePoint. If you have for instance a third-party app that creates documents in SuperOffice, you need to enable system user for storing documents in SharePoint. (You can't turn this on the first time you configure SharePoint documents. It must be fully configured first. Complete the configuration and start the wizard (Settings), navigate to step 3, and turn it on.)
Looking forward to hear your feedback :)
Hi Frode
Thank you for the detailed reply.
Good to have it confirmed that you can migrate documents from Microsoft 365 Document Integration (legacy) to SharePoint documents 2.x
As far as we can see enabling the system user for storing documents in SharePoint is working as it should. And apps that use this can write to SharePoint v2
However....There might be signed documents or other documents that for some reason have not been stored in SharePoint legacy. Since system user in SharePoint v2 is a rather new feature.
And a customer might have two document repositories?
So when migrating from SharePoint legacy to SharePoint V2, there are still unmoved documents in SO_arc Online. If this makes sense?
This is probably a fringe case, but if these documents are to be moved to SharePoint v2. The Migration tool can not move them, as that is "looking" to SharePoint legacy. Not SO_arc Online
In this case we need to wait for DataBridge to be able to import documents when a customer is using SharePoint v2. This is not supported at the moment.
Thanks for the feedback.
"There might be signed documents or other documents that for some reason have not been stored in SharePoint legacy."
- I assume this was stored in CRM while having SharePoint legacy configured. You may set where to store documents - in the template-property (SO admin) to store those documents elsewhere. If this is elsewhere than via the document-plugin - and what is supported ie. via some custom scenario - it needs to be resolved case-by-case. We would need more details to be able to assist.
"a customer might have two document repositories?"
- Yes - You may set where to store documents - in the template-property (SO admin) to store in / use multiple locations.
"there are still unmoved documents in SO_arc Online"
- I assume you refer to documents stored in CRM - which the 'sharepoint-documents-migration' is not able to move it to SharePoint V2. We would need more details to be able to assist. Send the json-error-log to us (pilot@..) and we can try to assist on why.
"The Migration tool can not move them, as that is "looking" to SharePoint legacy"
- If the document-plugin support it - and you are able to open it from CRM - the 'sharepoint-documents-migration' should be able to read it too. One possible case would be if those documents is not owned by a SuperOffice-user that are not SharePoint-user, - there is an option to skip those:
To include them - the 'sharepoint-documents-migration' will try to use the system-user to save it to SharePoint:
- Documents omitted
- Documents belonging to users without credentials and visible for on document is set to “me” are omitted.
- Documents belonging to users without credential (if that is ticked) is omitted.
- SuperOffice Document library (app) : Files.ReadWrite.All
- Create documents on behalf of non existing SharePoint user (system user)
Send the json-error-log to us, and we can try to assist on why.