top of page

LITIGATION SUPPORT TIP OF THE NIGHT

The views expressed in this blog are those of the owner and do not reflect the views or opinions of the owner’s employer. All content provided on this blog is for informational purposes only. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site. The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information. This policy is subject to change at any time. The owner is not an attorney, and nothing posted on this site should be construed as legal advice. Litigation Support Tip of the Night does not provide confirmation that any e-discovery technique or conduct is compliant with legal, regulatory, contractual or ethical requirements.

See my post on Running Regex Searches With a Grep Utility on the ILTA litigation support blog.

New tips for paralegals and litigation support profesionals are posted to this site each week. Click on the blog headings for better detail.

See How-To Videos on my YouTube channel.

Getting Office 365 Data into Relativity

Sean O'Shea
Jun 4, 2021
1 min read

Note that RelativityOne can import data directly from Office 365, keeping the data on Azure cloud servers during the import. Office 365's electronic discovery center will export the data from Outlook Exchange, SharePoint, and OneDrive, and Relativity Processing can import it.

Office 365's electronic discovery center will not provide metadata for .pst files, so they need to be imported with Relativity Processing.

RelativityOne Collect can be added as an application in Office 365.

Different metadata fields can be imported from Office 365 into Collect.