Last date modified: 2025-Oct-23

Blackout migration

Relativity now supports Blackout when using ARM to restore a workspace from Relativity Server to RelativityOne. Native redactions from Blackout are migrated to Redact during this process. The event handlers run when updating to the next version of Redact post-installation. The event handlers do not need to be configured and they will automatically update previously migrated Blackout workspaces.

Limitations

  • If you run an image markup project, you will need to re-HOCR each of the documents included in the project.
  • There are no longer any limitations related to the CorrelationId column.
  • If a user attempts to export an audit report from a server-migrated workspace and the table contains entries which map to Audit types that do not exist in Redact, the resulting audit will report the type as Unknown. The following audit types are marked as Unknown:
    • Image Markup Created using Find & Redact
    • Image Markup Created using Suggestions
    • Native Document Downloaded
    • Document Unlocked
    • Document Locked

Production preparation

The following considerations should be used for documents redacted in Blackout with the production preparation project. The production preparation project has been deprecated in Redact and native spreadsheet and PDF redactions are now burned in at the time of production.

For native spreadsheets and PDFs before the migration

These documents should be unlocked using the production preparation project as soon as possible, preferably by using Blackout before the migration. If you want to modify native redactions in Redact, you must also revert the production preparation project in Blackout before migration. If you want to produce the native redactions in Redact and the production preparation project has already been run in Blackout, you only need to run production in RelativityOne and then export the documents using Import/Export.

Some other considerations for these document types include:

  • To edit a markup in Redact that was burned in using Blackout, the markup must be reverted using the production prep project in Blackout or Redact.
  • Any markup burned in using Blackout will be produced in RelativityOne during production whether it was locked by production prep or not.
  • Locking a document does not affect anything in RelativityOne other than preventing a user from editing the markups. Locked documents have to be unlocked in either Blackout or Redact to edit the markups.

Unlocking documents in Redact or Blackout before migration

Documents are locked by production preparation projects to ensure that once the documents are produced, the desired markups are maintained. However, sometimes the circumstances in a case change and you are required to update previously produced documents. When needed, you can unlock documents to allow any user to edit or apply new markups to them.

The original native that has markups is no longer accessible after you unlock the project. As a result, we recommend creating a copy of the marked up native before unlocking the project.
If you unlock a production preparation project in Redact, the production preparation project will no longer be available.

To unlock documents that were previously produced by a project:

  1. Navigate to the Redact Projects tab and click on the project which contains the produced documents you wish to unlock.
  2. Click Unlock Project.
    The Unlock Project modal displays.
  3. Click OK.
    The unlock documents task is added to the queue and will begin running when agents are available. Once the task is complete, a message will display at the top of the screen when viewing a production preparation project indicating that the documents are unlocked.
If you run the project a second time, it will regenerate the extracted text over whatever was added to the field in the first run. Additionally, if you selected Retain a copy of the redacted file, an additional copy will be created during the second run.
Return to top of the page
Feedback