It seems like your browser didn't download the required fonts. Please revise your security settings and try again.


Starting May 1st, 2018, we will no longer offer the ArchiveOne family of products. This includes all editions of ArchiveOne, ArchiveOne for Files, Max Compression, and Access Security Manager. If you currently hold a maintenance and support contract, you will continue to receive our award-winning support until your contract expires, or until May 1st, 2019, whichever occurs first. The license for ArchiveOne is perpetual; therefore the software may continue to be used independently without any updates or support indefinitely.

How to Migrate from ArchiveOne to Barracuda Message Archiver

  • Last updated on


ArchiveOne Migration Admin Console

Shortcut on start menu: ArchiveOne Migrate to BMA

C:\Program Files (x86)\Barracuda\ArchiveOne\MigrateBMAService\MigrateBMAAdmin.exe

Logs in C:\Program Files (x86)\Barracuda\ArchiveOne\logs\MigrateBMAAdmin as MigrateBMAAdmin.log. Logs roll daily, not on each instance the ArchiveOne Migration admin console is opened.

INI Files

System_Migration.ini in LCS (C:\ProgramData\Barracuda\ArchiveOne\LocalConfigurationStore)

  • Used to keep track of any jobs that were disrupted to ensure these restart where they left off, i.e., after service crash.

The migrate to BMA functionality is primarily provided by the following three services:

  • ArchiveOne Migrate to Message Archiver
    • C:\Program Files (x86)\Barracuda\ArchiveOne\MigrateBMAService\AOneMigrateBMAService.exe
    • Dependency set on the ArchiveOne BMA Service.
    • Logs in \\localhost\Add-ins\AOnePol\logs\MigrateBMAService\<date_time> as MigrateBMAService.log
    • This service is new in v7.3.1.
  • ArchiveOne BMA Service (existing service)
    • C:\Program Files (x86)\Barracuda\ArchiveOne\BMAServer\AOneBMAService.exe
    • Logs in \\localhost\Add-ins\AOnePol\logs\AOneBMAService\<date_time> with separate functionality based subfolders.
    • This is an existing service.
  • ArchiveOne BMA Data Manager Service x64
    • C:\Program Files (x86)\Barracuda\ArchiveOne\BMAServer\AOneItemListBMAService.exe
    • This is an existing service.
C2CAOneConfig Database Tables
  1. BMAMigration
    1. Stores the fingerprint of successfully uploaded items returned from the BMA and along with the corresponding ArchiveOne Index ID. The state of the item may be one of the following:
      • ReadyToStub – Item suitable for stub conversion from ArchiveOne to BMA stub.
      • WillNotStub – Item unsuitable, for example: PST or journal items; message classes other than IPM.Note, IPM.Post, IPM.Note.Microsoft.Voicemail.UM, IPM.Note.Microsoft.Voicemail.UM.CA, IPM.Note.SMIME, or IPM.Note.SMIME.MultipartSigned.
      • Completed – ArchiveOne stub was converted to a BMA stub.
      • FailedToStub – Stub conversion was attempted but failed.
  2. BMAMigrationSyncFolders
    • Stores folder path information for each mailbox and a corresponding sync blob, which is sent to the BMA to identify the folder path. This ensures the BMA has the folder location for each migrated item.
  3. BMAMigrationSyncStores
    • Stores mailbox information for each archived mailbox to be migrated to the BMA and a corresponding sync blob, which is sent to the BMA to identify the mailbox in question. For live mailboxes, this table is seeded: ArchiveOne logs into the mailbox and pre-populates this table and the BMAMigrationSyncFolders table with all the live mailbox folders. The store type indicates whether this a journal mailbox, an end user mailbox or a PST file.

Stage 1: Upload Process

For more information, see Upload Process.

Stage 2: Stubbing

For more information, see Stubbing.

Common Errors found in Logs

For more information, see Known Errors.


Audit .csv files are stored in C:\ProgramData\Barracuda\ArchiveOne\MigrationAudit. Migration (data upload to BMA) and partition file processing are per repository, and are divided into migration success/failure (each message audited) and partition success/failure (each partition file audited), e.g.:

  • Year_2015_MigrationFailure.csv
  • Year_2015_MigrationSuccess.csv
  • Year_2015_PartitionSuccess.csv
  • Year_2015_PartitionFailure.csv
  • Year_2016_MigrationSuccess.csv
  • Year_2016_PartitionSuccess.csv

Stubbing is audited across all repositories as StubbingSuccess.csv and StubbingFailure.csv.

Failure files are only present if there are failures to audit, and will give the returned error code. If there are no failures to date, then these files will not be present.

Currently, audit files do not roll over (and therefore may become very large).


Report .txt files are stored in \\localhost\Add-Ins\AOnePol\MigrationReports. These are the output of the Migration tool status view when an individual repository is completed, and when the current migration job as a whole completes, e.g.:

  • <date>_<time>.txt
  • <date>_<time>_<repository_name>.txt