Documentation

# NextMatters migration connector

Migrates documents from NextMatters (opens new window) legal case management system to SharePoint.

DLL: Epona.Migrate.NextMatters.dll

# What it does

  • Matter and document retrieval — reads matters and documents from NextMatters database
  • Document version support — preserves document version history
  • Metadata extraction — retrieves document properties, categories, and custom fields
  • Batch upload — transfers documents to SharePoint with full version information
  • Matter mapping — maps NextMatters matters to SharePoint matter structure
  • User mapping — translates NextMatters user accounts to SharePoint logins
  • Error recovery — detailed logging for troubleshooting migration issues

# Prerequisites

  • NextMatters SQL Server database accessible
  • Database credentials with read access
  • Network connectivity to NextMatters database server
  • File system access to NextMatters document storage directories
  • Target SharePoint site collection provisioned with document libraries

# Deployment

  1. Copy Epona.Migrate.NextMatters.dll to the Epona.Migrate application directory
  2. Restart Epona.Migrate or reload connectors
  3. Configure NextMatters connection settings in the migration UI

# Configuration

# Connection settings

# DbServer

  • Type: string
  • Default: —
  • Description: NextMatters SQL Server hostname

# DbPort

  • Type: int
  • Default: —
  • Description: Optional SQL Server port number

# DbDatabase

  • Type: string
  • Default: —
  • Description: NextMatters database name

# DbUserName

  • Type: string
  • Default: —
  • Description: Database login username

# DbPassword

  • Type: string
  • Default: —
  • Description: Database login password (encrypted)

# TimeZone

  • Type: int
  • Default: 4
  • Description: Timezone offset for date conversions

# SourceDirectory

  • Type: string
  • Default: —
  • Description: Root directory for NextMatters document storage

# Date handling

# UseCreateDateFromDatabase

  • Type: boolean
  • Default: false
  • Description: Use database created date instead of filesystem date

# UseModifyDateFromDatabase

  • Type: boolean
  • Default: false
  • Description: Use database modified date instead of filesystem date

# Folder and path mapping

# ReplaceFolders

  • Type: string
  • Description: Path mapping configuration for folder structure changes (format: oldpath=newpath;)

# Metadata mapping

# MapDocumentNumber

  • Type: string
  • Description: SharePoint column name for document number (without version)

# MapDocumentNumberVersion

  • Type: string
  • Description: SharePoint column name for document number with version

# MapDocumentCategory

  • Type: string
  • Description: SharePoint column name for document category

# MapDocumentVerzondenDatum

  • Type: string
  • Description: SharePoint column name for document sent date

# DocumentTypeCategories

  • Type: string
  • Description: Maps NextMatters document type categories to SharePoint values

# User mapping

# MapUsernames

  • Type: string
  • Description: Maps NextMatters usernames to SharePoint login names (format: nextmattersuser=sharepointlogin;)

# Migration workflow

  1. Connect — authenticate to NextMatters database
  2. Scan — enumerate matters and documents from SQL database
  3. Validate — verify matter mapping and user translation
  4. Plan — review scope, date handling, and target libraries
  5. Execute — transfer documents with versions and metadata to SharePoint
  6. Verify — validate completeness and log any errors

# NextMatters specific features

# Matter structure

NextMatters matters are organized by year in the source directory. The migration connector:

  • Enumerates matters from the database
  • Locates documents in the file system using the configured SourceDirectory
  • Maps matter codes and names to SharePoint matter structure

# Document versions

The connector preserves document versions:

  • Reads version history from the NextMatters database
  • Uploads each version to SharePoint
  • Maintains version metadata and modification dates
  • Sets proper document number with version suffix

# Metadata preservation

NextMatters metadata is mapped to SharePoint columns:

  • Document number — unique identifier within matter
  • Document version — version suffix or number
  • Document category — classification or type from NextMatters
  • Sent date — document sent or dispatch date
  • Custom fields — any additional NextMatters fields configured in mapping

# Date handling

NextMatters stores both filesystem and database dates:

  • Filesystem dates — from file creation/modification times (default)
  • Database dates — more reliable for documents with moved/restored files
  • Timezone offset — configurable for systems with timezone differences

# Troubleshooting

# Common issues

# Cannot connect to database

  • Cause: Network or authentication issue
  • Resolution: Verify database server address, database name, and credentials

# Documents not found

  • Cause: SourceDirectory path incorrect
  • Resolution: Verify path exists and contains matter subdirectories

# Version data missing

  • Cause: UseCreateDateFromDatabase not enabled
  • Resolution: Enable database date options for reliable version dating

# User mapping fails

  • Cause: Username mismatch
  • Resolution: Verify NextMatters usernames match SharePoint login format

# Metadata not transferring

  • Cause: Column name mapping incorrect
  • Resolution: Ensure SharePoint column names match exactly; verify custom fields exist
Last Updated: 4/2/2026, 11:46:36 AM