Aryson OST Converter Tool

Step 4: Mark the Export to Email Clients radio button and select Microsoft 365 as the destination.

Step 5: Authenticate an active Microsoft 365 account

You may choose the A or B login method to log in to the Microsoft 365 account using valid credentials.

1. Use OAuth 2.0 authentication

1. Enter your Microsoft admin account email and click on Authenticate.

2. Log In To Your Account

1. Select an Account
   • In the Pick an account window, click the Microsoft account you want to use.
   • Alternatively, select Use another account if your account is not listed.
2. Provide your password and click Sign in.
3. Approve Multi-Factor Authentication (MFA)
   • If prompted, open the Microsoft Authenticator app on your mobile device.
   • Approve the sign-in request.
   • If a matching number is displayed (e.g., 53), enter that number in the Authenticator app and approve the request.
4. Authentication Successful
   • Once verification is completed, a confirmation message will appear: "Authentication complete. You can close the browser and return to the application."
   • Close the browser window.

Note: While selecting the Office 365 account in the browser window, make sure you have already logged in to the required account before.

Note: Sign in to the required Microsoft 365 account in your browser before starting the migration. If multiple browser windows are open with different accounts, use the one where the required Microsoft ID is already logged in, as authentication will proceed only in that browser.

2. Use an Application Credential

1. Disable Use OAuth 2.0 Authentication.
2. Enter the Microsoft 365 Admin Account, Application (Client) ID, Client Secret, and Tenant ID to authenticate the connection.

Enter Azure Application Details

Fill in the following information from your Azure app registration:

If you choose Application Credentials Authentication (Client ID, Client Secret, and Tenant ID), you must first create an Azure App Registration and assign the required API permissions in Microsoft Entra ID (Azure AD).

For complete instructions on creating the Azure Active Directory application and enabling API permissions, visit:

Create Azure Active Directory and Enable API Permission Guide

In the guide at step 17, you need to add the required API permissions. The image below lists all the API permissions that must be configured for successful authentication and migration.

3. After generating the credentials, fill in the required fields and click on Authenticate.

B. 1: Choose Mailbox Mapping Mode

• Migrate All Files to Selected Mailbox(es): Transfer all selected files into the same destination Microsoft 365 mailbox(es).
• Map Each File to Specific Mailbox(es): Assign individual files to different Microsoft 365 mailboxes before migration.
• Next: After selecting the preferred mapping mode, click Next to continue with mailbox mapping and migration.

B 1.1: Migrate All Files to Selected Mailbox(es):

Select Destination: Microsoft 365 Mailboxes

• Automatic Fetch Users: Retrieve all mailboxes from the authenticated Microsoft 365 tenant automatically.
• CSV Import (Optional): Import specific mailbox users using a CSV file.
• Search User: Locate a mailbox quickly using the search option.
• Review User Details: Verify Name, User ID, Mailbox Type, and Validation Status.
• Select Mailboxes: Choose the required destination mailboxes or use Select All.
• Verify Validation: Ensure the selected mailboxes display Allowed status.
• Next: Click Next to proceed with mailbox mapping and migration.

Note:

• Allowed indicates a licensed and valid mailbox, while Denied indicates a non-licensed or invalid mailbox.
• Mailbox types may include User Mailbox and Shared Mailbox.
• Only mailboxes with Allowed status can be selected as migration destinations.

Import Users via CSV

1. Enable CSV import and download the sample CSV template.
2. Enter mailbox details in the required format and save the file.
3. Click Import CSV and browse to the updated CSV file.
4. Review the imported users and verify their validation status.
5. Select the required mailboxes and click Next to continue.

B.1.2: Map Each File to Specific Mailbox(es):

1. Review Loaded Folders: Verify your retrieved folders under the Source Folder column and ensure all mailboxes are loaded successfully.
2. Map Target Mailboxes: Click the -- Select Target Mailboxes -- dropdown next to each folder to map its destination.
   • Select the corresponding target Microsoft 365 mailbox from the mailbox list.
   • Use the Search Users option to quickly find destination mailboxes.
   • Verify the UPN and mailbox type before mapping.
   • Check licensed mailboxes to ensure they are ready for migration.
   • Click Select All to map multiple mailboxes at once.
   • Review the mailbox summary (All, Licensed, Unlicensed) for validation.
   • Click Apply to save the mappings and proceed with migration.
3. Filter Selection: Use the checkboxes on the right (or toggle Select All ) to exclude any folders you do not want to migrate.
4. CSV Import (Optional): Click the CSV Import button to upload a mapping file if you are migrating multiple users' profiles at once.

5. Save and Migrate: Click Save Mapping & Start >> to lock in your folder configuration and begin the migration process.

Step 6: Return to the Application & Configure Migration Settings & Filters

• Date Range Filter: Enable and specify a Start Date and End Date to migrate only emails within a particular time period.
• Custom Output Folder: Select a specific destination folder to store migrated data instead of the default location.
• Skip Existing Exports: Exclude previously migrated items to prevent duplicates and reduce migration time.
• Follow Tree Hierarchy: Maintain the original mailbox folder structure throughout the migration process.
• Map with Default Mailboxes: Automatically map source default folders to their corresponding default folders in the target mailbox.

Step 7: Configure Advanced Migration Filters

• Attachment Handling: Enable this option to manage email attachments during migration. Choose to exclude attachments based on migration requirements.
• Duplicate Detection: Enable duplicate filtering to prevent redundant email migration. Compare items using attributes such as To, From, Subject, Body, and CC fields for accurate duplicate identification.

Step 8: Click Start Export to begin the OST/PST to Office 365 migration conversion process.

Step 9: Monitor and Complete the Conversion Process

After clicking Start Export, track the migration progress and review the conversion details in real time.

• Source & Destination: View the selected source file and target export location.
• File Count & Total Messages: Monitor the number of processed files and emails.
• Processing Status: Check the current status of the export operation.
• Execution Time: Track the total time taken for the conversion.
• Output Location: Verify where the converted data is being saved.
• Progress Bar: Monitor overall conversion progress in real time.
• Stop Process: Cancel the export operation if required.

Step 10: Once the conversion completes, the software displays, “All selected data has been exported successfully." You can even use the additional options to proceed further.

• Export Log: Open the detailed log report to verify the export process and results.
• Start New Export: Begin another OST conversion or migration task if required.

Step 4: Mark the Export to Email Clients radio button and select IMAP as the destination.

Step 5: Configure IMAP Server and Authenticate

1. Enter the destination Email Address.
2. Provide the App Password or mailbox password.
3. Specify the IMAP Server Host and IMAP Port Number.
4. Click on Server List option to fetch supported IMAP server details automatically.
   • Select the IMAP host as desired or search for a specific one and click Continue.

5. Enable Show Credentials to verify the entered password.
6. Click Authenticate to validate the mailbox connection and proceed with the migration.

Step 6: Apply the Additional Features of the Software

1. Configure General Export Settings

• Date Range Filter: Migrate emails within a specific date range.
• Custom Output Folder: Specify a folder to save migration logs and reports.
• Skip Existing Exports: Avoid migrating items that already exist in the destination mailbox.

2. Attachment Handling: Exclude attachments during the migration.
3. Duplicate Detection: Skip duplicate emails based on To, From, Subject, Body, and CC fields.

Step 7: Click on the Start Export button to begin the OST/PST to IMAP migration.

Step 8: Monitor and Complete the Conversion Process

After clicking Start Export, track the migration progress and review the conversion details in real time.

• Source & Destination: View the selected source file and target export location.
• File Count & Total Messages: Monitor the number of processed files and emails.
• Processing Status: Check the current status of the export operation.
• Execution Time: Track the total time taken for the conversion.
• Output Location: Verify where the converted data is being saved.
• Progress Bar: Monitor overall conversion progress in real time.
• Stop Process: Cancel the export operation if required.

Step 9: Once the conversion completes, the software displays, “All selected data has been exported successfully." You can even use the additional options to proceed further.

• Export Log: Open the detailed log report to verify the export process and results.
• Start New Export: Begin another OST conversion or migration task if required.

Step 4: Select Google Workspace under the Export to Email Clients drop-down list.

Step 5: Authenticate your Google Workspace account.

Log in via the Workspace admin account and JSON key, and click Authenticate.

You can generate a JSON file with the help of the detailed guide.

Step 6: Map Source Files to Google Workspace User Accounts

Associate the selected source file with the corresponding Google Workspace mailbox before starting the migration.

1. Select the imported source file from the mapping list.
2. Click Select Directory Users and choose the target Google Workspace user account.
   • Search or select the required User ID to map and click Apply.

3. Alternatively, you can import a CSV file for bulk user mapping.

• Click on the Sample CSV button to save a demo CSV file.
• Afterwards, click on the Import CSV button to import the saved CSV file.

• Click ok and click on Select CSV users.
• Select the required user IDs of the users and click Apply.

Step 7: Configure Migration Settings

1. Apply the General Filters:

• Date Range Filter: Migrate emails within a specified start and end date range.
• Custom Output Folder: Specify a location to store migration logs and reports.
• Skip Existing Exports: Prevent duplicate migration of items already present in the destination account.
• Follow Tree Hierarchy: Preserve the original mailbox folder structure during migration.
• Mapped with Default Mailboxes: Automatically map source default folders to default mailbox folders.

2. Apply the Advanced Filters:

• Attachment Handling: Exclude attachments during the migration.
• Duplicate Detection: Identify and skip duplicate emails based on fields such as To, From, Subject, Body, and CC.

Step 8: Click on the Start Export button to begin the OST/PST to Google Workspace migration.

Step 9: Monitor and Complete the Conversion Process

After clicking Start Export, track the migration progress and review the conversion details in real time.

• Source & Destination: View the selected source file and target export location.
• File Count & Total Messages: Monitor the number of processed files and emails.
• Processing Status: Check the current status of the export operation.
• Execution Time: Track the total time taken for the conversion.
• Output Location: Verify where the converted data is being saved.
• Progress Bar: Monitor overall conversion progress in real time.
• Stop Process: Cancel the export operation if required.

Step 10: Once the conversion completes, the software displays, “All selected data has been exported successfully." You can even use the additional options to proceed further.

• Export Log: Open the detailed log report to verify the export process and results.
• Start New Export: Begin another OST conversion or migration task if required.