How to perform a migration to SharePoint Online

High level step-by-step process of a data migration with Xill 4.

1. Extraction
   1. Extract the content using a source connector from the accelerator library you can find a list of all source connectors at this link https://xillio.community/accelerators.
   2. Configure the connector according to the documentation which can be found at this link: https://docs.xill.io/xill4/category/source-accelerators/.
   3. Run the source connector and begin extracting content into the content store specified in the “mongoConnection” flow variable of the source connector.
   4. Keep an eye on the console of the source connector for any errors that may occur.
   5. Once the extraction is complete, download the extraction report accelerator from the accelerator library which can be found under “framework” accelerators at this link: https://xillio.community/accelerators.
   6. Configure the extraction report accelerator according to the documentation which can be found at this link: https://docs.xill.io/xill4/accelerators/framework/extraction-report/.
   7. Run the extraction report. This will generate an excel report of all extracted documents of kind RECORD and CONTAINER. Share the report with the client and ask them to validate and formally sign-off on the extraction.
2. Analysis
   1. Now that you have performed a successful extraction, it’s time to analyse the extracted content using Xillio insights.
   2. Download and install ElasticSearch and Kibana on the Insights server.
   3. Download the Xillio Insights accelerator from the accelerator library which can be found under “framework” accelerators at this link: https://xillio.community/accelerators.
   4. Configure the insights accelerator according to the documentation which can be found at this link: https://docs.xill.io/xill4/accelerators/framework/insights/.
   5. Run the first flow of the accelerator, which performs an analysis of the extracted data before ingestion into insights.
   6. Once the first flow is complete, run the second flow which ingests the analysed data into Xillio Insights.
   7. The ingested data can be found in Kibana, under the same index name specified in your “Ingestion” flow.
   8. Find the .ndjson file in the folder which contains the insights accelerator and upload the .ndjson file into Insights.
   9. Assign the data view associated with your data index to the visualisations in the dashboards you’ve uploaded. This will allow the dashboards to read from the data stored in your data index.
   10. Once you have gone through all the dashboards and have an understanding of the data, schedule an insights session with the client to take them through the analysis.
   11. Most importantly, point out any potential blockers to migrating to the target. For example, if you are migration to SharePoint online, check for invalid characters in the file names, or file paths longer than 400…etc

3. Transformations

1. Metadata mapping: Provide the client with a list of all extracted metadata fields from the source system and ask them to map each of the fields to a target field in the target system. An example of a metadata mapping sheet can be found in the transformation accelerator which can be downloaded at this link: https://xillio.community/accelerators/
2. Once the metadata mapping exercise is complete, ask the client to verify that the target fields mapped in the sheet are an exact match to the fields that have been created in the target system. If there is any deviation in this regard, the mapping exercise will fail.
3. Structure mapping: Provide the client with a list of all extracted folders from the source system, along with their source IDs and ask the client to map the folders from the source system to a target structure in the target system. An example of a metadata mapping sheet can be found in the transformation accelerator which can be downloaded at this link: https://xillio.community/accelerators/
4. Once the structure mapping exercise is complete, ask the client to verify that the target structure mapped in the sheet is identical to the target structure which has been created in the target system. If there is any deviation in this regard, the structure mapping exercise will fail.
5. Principal mapping: If the users in your content store do not already have an email address associated with them, generate a list of all users in your content store with their source IDs and ask the client to assign the email addresses of all relevant users as they are specified in the target system. Please read the documentation on the principal mapping which can be found at this link (section 6): https://docs.xill.io/xill4/accelerators/framework/transformation/
6. Run the flows in the transformation accelerator according to the documentation which can be found at this link: https://docs.xill.io/xill4/accelerators/framework/transformation/
7. Now that your transformations have been executed, it’s time to validate them by running the Prepare flow, which is the first flow of the target connector. This flow will validate your transformations and throw errors if any misalignment occurs.  As a rule of thumb, you must never proceed to importing data to the target until the prepare flow can run from start to finish without throwing any errors. The documentation on the SharePoint target connector can be found here: https://docs.xill.io/xill4/accelerators/target/sharepoint-online/