How to Migrate Lexbe eDiscovery Data to GoldFynch: A Practical Import Guide

03 September 2026 by Carey eDiscovery case-migration

Takeaway: Migrating Lexbe eDiscovery data to GoldFynch does not mean rebuilding your case from scratch. Lexbe can export standard load-file productions containing native files, text, metadata, images, and custom coding fields. With the right export and a quick validation step, that data can be imported into GoldFynch while preserving the information your legal team still needs.

Moving an eDiscovery case to a new platform can feel complicated, especially when the matter includes years of metadata, coding, redactions, and review work. Fortunately, migrating Lexbe eDiscovery data to GoldFynch can be relatively straightforward. The key is to export the case in a standard format, preserve the fields that matter, and validate the data before completing the move.

What is Lexbe eDiscovery?

Founded in 2006, Lexbe was an early cloud-based eDiscovery provider focused on helping law firms and litigation teams manage document-heavy matters without having to maintain their own eDiscovery infrastructure.

Its Lexbe eDiscovery Platform includes tools for processing, searching, reviewing, tagging, redaction, document production, privilege logging, analytics, and other common litigation workflows.

If you are currently using Lexbe and are looking to migrate to another eDiscovery software platform, much of your case data can be exported in standard eDiscovery formats. That makes it possible to move the documents, metadata, and review work that matter without having to start the case from scratch.

What data might be inside a Lexbe case?

A Lexbe case usually contains much more than the documents visible in the document viewer.

The underlying files and metadata

Depending on the matter, the case may contain:

Native Word, Excel, PDF, email, and other files
PDFs or TIFF document renderings
Extracted text and OCR
Email sender, recipient, subject, and date metadata
Custodian information
Email family and attachment relationships
Bates and control numbers

Review work product

The workspace may also contain information created during review, including:

Responsiveness coding
Privilege coding
Confidentiality designations
Custom tags and coding fields
Reviewer notes
Redactions
Translations
Previous production information

Lexbe supports both built-in document fields and user-created custom coding fields. These may contain important case knowledge, so they should be considered before the migration begins.

Start by deciding what you actually need to migrate

Before creating a Lexbe export, take a quick inventory of the case.

Identify the important case data

Record basic information such as:

Document count
Custodians
Bates ranges
Existing productions
Important custom fields
Privilege and responsiveness coding

For an active case, you will usually want to preserve the native files, searchable text, metadata, email families, review coding, and relevant production information.

Avoid moving unnecessary workspace clutter

You do not necessarily need to reproduce every saved search, temporary tag, or intermediate workflow from the old platform. The goal is to preserve the information needed to continue reviewing, searching, and producing the case in GoldFynch.

For older or closed matters, that may mean exporting considerably less.

Export Lexbe data as a load-file production

This is where migrating from Lexbe becomes easier. Lexbe can create fairly standard eDiscovery productions, making the data more portable across platforms.

What a Lexbe production can contain

Depending on how the production is configured, the export may include folders for:

Native or original files
PDFs
Extracted text
TIFF or other images
Load files

Lexbe supports several load-file formats, including:

Concordance .DAT
Opticon .OPT
Summation .DII
Excel .XLSX
Tab-delimited .TSV
Other text-based load files

Use a standard load-file structure

For a migration to GoldFynch, a Concordance-style DAT load file, accompanied by the native files, extracted text, and relevant document images, is usually one of the most portable options. GoldFynch can import standard load-file productions and associate external metadata with the corresponding documents.

Keep the production folder structure intact when moving or ZIPping the export. The paths in the DAT or OPT files need to continue pointing to the correct native, text, and image files.

Do not forget Lexbe custom fields and tags

This is one of the most important Lexbe-specific migration considerations. Lexbe allows teams to create their own coding sections and fields. These can become valuable review work product over the life of a case.

Custom fields may contain important case decisions

For example, a team may create fields for case issues such as damages, liability, and contract terms. Or for depositions based on the person involved. Other fields might track privilege, witness relevance, hot documents, deposition exhibits, or factual issues.

If attorneys and reviewers have been relying on these fields, exporting only Lexbe’s standard metadata could leave important work behind.

Include those fields in the load file

Lexbe allows users to customize which fields are included in production load files. Before exporting the case, review the available built-in and custom fields and include the ones you want to preserve, if possible. Otherwise, you can export it as a CSV file separately.

Where possible, keep different review decisions in separate columns. For example:

PRIVILEGED
KEY_DOCUMENT
DEPONENT_SMITH
DAMAGES

This makes the information easier to interpret and map after the migration.

Recreate review coding in GoldFynch where needed

GoldFynch can accept external custom metadata through load files such as DAT or CSV. During the migration, some Lexbe fields may be best retained as metadata, while others may make more sense as GoldFynch tags for continued review.

The important step is to preserve the original values during export so that nothing important is lost before you decide how to organize it in the new case.

Pay special attention to email families

Email relationships are another area worth checking closely. A single email may have several attachments, and reviewers often rely on those relationships when determining responsiveness or privilege.

Preserve parent and attachment information

Lexbe load files can include fields that identify parent documents, attachments, and family relationships, as well as email metadata such as From, To, CC, BCC, Subject, Custodian, and Sent date.

Include these fields wherever possible so that email file families can be reconstructed correctly after the import. Splitting an email from its attachments can make future review unnecessarily difficult, especially if coding was applied at the family level.

Check redactions, translations, and other rendered files

Not every part of the case should be migrated using the original native file alone.

Redacted documents: If a document has already been redacted in Lexbe, ensure the export includes the rendered version with the approved redactions. This ensures that your work is preserved.
Translated documents: If translated documents are part of the matter, include them in the export as well. Keeping these files alongside the production helps maintain the relationship between the original and translated versions.
Reviewer notes and platform-specific information: Reviewer annotations, notes, or other Lexbe-specific workspace information may not always transfer as cleanly as normal metadata. If this information is important to the case, confirm how it appears in the export before closing the Lexbe workspace.

Importing the Lexbe production into GoldFynch

Once the Lexbe export has been prepared, importing it into GoldFynch is relatively straightforward.

1. Upload the complete production

Keep the production folders together and ZIP them without rearranging the contents.

Then:

Create or open the destination case in GoldFynch.
Upload the complete Lexbe production ZIP.
Start a Production Import.
Select the uploaded production.
Review the document and metadata options.
Submit the import for further processing by the GoldFynch team.

GoldFynch can use the existing document renderings where appropriate or generate new ones depending on the import settings. Using the supplied renderings can be particularly useful when you want to preserve Bates numbers, endorsements, or redactions exactly as they appeared in Lexbe.

For very large migrations, GoldFynch also offers alternative transfer options, including FTP-based uploads.

2. Review the metadata mapping

As part of the import process, pay attention to how Lexbe metadata and custom fields are mapped. This is especially important if the production contains custom review coding that you want to continue using in GoldFynch.

Test before moving every Lexbe case

For a large or active matter, avoid making the first migration attempt with the entire case. Start with a representative sample instead.

Choose documents that test the difficult parts

Include examples such as:

Emails with attachments
Privileged documents
Custom-coded documents
Redacted documents
Previously produced documents
Documents containing important metadata

Compare the results

After importing the sample into GoldFynch, compare it against the same documents in Lexbe.

Check:

Metadata
Family relationships
Bates values
Searchable text
Redactions
Native files

Also, cross-check the fields flagged earlier. If all the elements look correct, you can proceed with the remainder of the case with much more confidence.

Moving your Lexbe case to GoldFynch

Migrating eDiscovery platforms is not simply a matter of copying files. The real task is preserving the review work and metadata that make those files useful. Fortunately, Lexbe’s support for standard load-file productions makes that process more manageable.

By exporting the relevant native files, text, metadata, family information, redactions, and custom coding fields, you can import the key parts of the case into GoldFynch without having to rebuild the matter from the beginning. GoldFynch has an easy browser-based workflow that lets you review documents, tag them, make redactions, and create productions.

If you are considering a Lexbe eDiscovery migration, try GoldFynch.

GoldFynch is a modern cloud-based platform that offers drag-and-drop uploads, easy review, unlimited productions and sharing, and predictable, pay-as-you-go pricing. Sign up for a free case or schedule a demo to see how it can fit your eDiscovery workflow.

It costs just $27 a month for a 3 GB case: That’s significantly less than most comparable software. With GoldFynch, you know exactly what you’re paying for: its pricing is simple and readily available on the website.
It’s easy to budget for. GoldFynch charges only for storage (processing files is free). So, choose from a range of plans (3 GB to 150+ GB) and know up-front how much you’ll be paying. You can upload and cull as much data as you want as long as you stay below your storage limit. And even if you do cross the limit, you can upgrade your plan with just a few clicks. Also, billing is prorated – so you’ll pay only for the time you spend on any given plan. With legacy software, pricing is much less predictable.
It takes just minutes to get going. GoldFynch runs in the Cloud, so you use it through your web browser (Google Chrome recommended). No installation. No sales calls or emails. Plus, you get a free trial case (0.5 GB of data and a processing cap of 1 GB) without adding a credit card.
It’s simple to use. Many eDiscovery applications take hours to master. GoldFynch takes minutes. It handles a lot of complex processing in the background, but what you see is minimal and intuitive. Just drag-and-drop your files into GoldFynch, and you’re good to go. Plus, you get prompt and reliable tech support (our average response time is 30 minutes).
Access it from anywhere, and 24/7. All your files are backed up and secure in the Cloud.

Want to find out more about GoldFynch?

Schedule a Demo