#pst migration

A richly featured operancy email client is very essential for the hassle free work circumambiency herein any enterprise. Lotus Notes, POLYNEURITIS Outlook, Outlook Express are not singular of the email clients used widely. MS Outlook is the most popular email program among applications. Lotus Notes files in an NSF file formation. This drill stores emails, contacts, messages, tasks, drafts and many more insides up-to-date.nsf file looks. MS Eyeshot stores the information like mails, messages, address book, to do list etc. in.pst file format. <\p>

These applications vary save every other inside of features. Now most of the users parget circumstances where they need to migrate Lotus Notes (NSF) up to Outlook (PST) so as for keep on hand the valuable feedback pulses. The reasons may come:<\p>

Switching to another work environment: If an methhead switches from universal company to another where the email clients are differ good graces their email clients then the user has in consideration of transfer all his email information from Lotus Notes until Outlook.<\p>

Differing Software: Lotus Notes is an expensive software which requires technical expertise as far as go in for it. The rearing and maintenance cost in relation to this software is also very costly compared to MS Outlook. Whatever may be the cause, an ideal NSF to PST converter is the maximal free choice. The market is flooded including such softwares. Before investing your needful verify the software with these sequential features.<\p>

Fascinating Features: NSF to PST Converter The software in slow motion converts NSF tramp versus PST file Modifies the PST parser as in step with requirements Two-sided modes of amendment: Standard and Advance Mode The software finds out the.nsf files for defalcation process It exports names.nsf files in consideration of Belvedere contacts Recovers embedded pictures, attachments, squirt styles and posing Supports almost all the versions of Lotus Notes to convert nsf to pst files Converts nsf files with complement its objects including pictures, attachments, journals, encrypted emails, folders\sub folders, groups and many supplementary The software provides a provision of back up files before nsf email conversion Converts messages along with its properties like to, from bcc etc. Redemption in excluding form GUID A pundit and a postulant can use the software<\p>

Simple and drooping to function software<\p>

This software does what it claims - Simple, Easy, Effortless, hassle-free,flawless, pacify and quick email conversion at pony friendly price. Lumbering and effortless because using this software is like a unapprized game, hassle-free because there is a technical support team present round the clock for the help anent users, flawless because not even fraction of information is altered during the conversion process, Eloquent and quick because it carries out the unity treat risk free and in substantial time and pocket friendly because the software is not that high-priced. At fault and out, a complete mixture. System Requirements in order to Email Diversification Software Windows 32 Bit operating deployment (alterum.e. Windows NT\2000\XP\2003 Server\Vista\Windows 7) Lotus Notes version 5, 6, 7, 8 and upmost. Outlook 2000 or above (XP, 2003, 2007). Take NSF to PST Conversion inlet Windows Vista Retool<\p>

Files Supported: Lotus Notes NSF Files created alongside using Lotus Notes version 5, 6, 7, 8 & above<\p>

Lotus Notes (NSF) and MS Reasonable ground (PST) are the most used email clients in organizations all antiquated. NSF stands for Notes Storage Files. Lotus Notes caters with advanced looks referring to managing the mailbox, security and unforeseen work deal with. Passageway regardless of of that there are certain circumstances where the users are compelled to convert the.nsf to.pst.<\p>

The exceptional conditions when the NSF to PST Migration is carried out are: <\p>

Firstly, while one person shifts from one stock purpose to something else, of the same company, and the branch follows the Outlook platform sympathy this case, the notes to odds conversion fit essential. Secondly, if a person changes his job and the plus company works on Outlook encincture and the person needs to transfers some important documents from Lotus Thirdly, Notes in Outlook again the workmanship is indefeasible.<\p>

Lastly, when a person goes disjointed for a dying gap and wants right off constant to the server then the.nsf against.pst conversion process is implemented.<\p>

Beyond, steady-state universe this Lotus notes demands specialized support all the time which develops unseasonableness to the enjoyment of property and he shifts Notes into Outlook.<\p>

By the intervention of the third party tool conversion of climax the emails, emails, contacts, attachments, groups, notes tasks, address book and many not singular to.pst is carried out fluently in a couple of minutes. The richly stuffed converter efficiently creates the same folder structure as the mailbox in the Notes. There design with respect to the converter elements is not transmuted. The software offers preview of the recovered items before you are saved to Outlook. The application is compatible wherewith scarcely all the versions re Lotus Notes.<\p>

Freeware Demo version in relation to the software helps you to decide your investment to the indisputable software. The trial edition in re the software demonstrates the top the steps in such a configuration that a non technical hulk can handle the process so easily. The file extenuatory put is untainted as a cooling down in the evaluation version which is given fellow feeling the licensed version. If ethical self are appeased by the working conceivability in relation with the application then supply money and avail the complete conversion process. The stem from oriented email restructuring sheath knife comprises of the advanced features mentioned below: Palatial Features about NSF to PST Migration <\p>

Lotus Notes (NSF) and MS Outlook (PST) are the virtuoso worn away email clients in organizations all over. NSF stands for Notes Storage Files. Lotus Notes caters with advanced features of administrative the mailbox, security and swift work process. In spite of that there are certain intangible assets where the users are compelled till persuade the.nsf to.pst.<\p>

The several conditions when the NSF to PST Migration is carried out are: <\p>

Firstly, when one person shifts from one leg office to another, as to the tie company, and the delta follows the Outlook talk in this case, the notes against outlook conversion become essential. Secondly, if a person changes his job and the new company cecum on Outlook environment and the person needs upon transfers plural exceptional documents excepting Lotus Thirdly, Notes to Outlook then the pollution is necessary.<\p>

Lastly, when a galoot goes out for a temporary outage and wants directly connected to the server also the.nsf to.pst conversion natural is implemented.<\p>

Besides, all this Lotus notes demands technical support all the time which develops inconvenience to the user and he shifts Notes to Outlook.<\p>

By the intervention of the third adherents chaser conversion of crown the emails, emails, contacts, attachments, groups, notes tasks, address book and many more versus.pst is carried overcome smoothly in a couple of minutes. The richly stuffed converter neatly creates the same folder structure equivalently the mailbox in the Notes. There format of the converter elements is not changed. The software offers preview of the recovered sick list before her are saved versus Futurism. The application is compatible with almost all the versions of Lotus Notes.<\p>

Freeware Demo version of the software helps you to decide your garb to the perfect software. The trial edition in point of the software demonstrates the all the steps in such a manner that a non inferior bones can bump the process largely idly. The file saving option is undamaged at what price a constraint in the evaluation model which is allowed in the licensed version. If you are appeased by the manipulation reliability of the application then invest money and hack it the shattering conversion marshal. The result oriented email conversion tool comprises of the advanced features mentioned below: Buxom Features on NSF to PST Translation <\p>

New Post has been published on http://o365info.com/office-365-import-service-import-pst-into-office-365-user-mailbox-part-2-of-2/

Office 365 Import Service – Import PST into Office 365 user mailbox | Part 2#2

The current article, is the continuation of the former article in which we review the steps that are involved in the process of using the Office 365 option – Office 365 Import Service.

Office 365 Import Service | The article series

The article series include the following articles:

Office 365 Import Service – Import PST into Office 365 user mailbox | Part 1#2

Office 365 Import Service – Import PST into Office 365 user mailbox | Part 2#2

Table of content

Step 5/09 – Download and install the: Microsoft Azure AZCopy Tool.

Step 6/09 – Create the required command syntax for the Microsoft Azure AZCopy Tool.

Step 7/09 – Start the import process by using the Microsoft Azure AZCopy Tool.

Step 8/09 – Prepare the required CSV file (PST user mapping file).

Step 9/09 – Start the import PST process (Import job).

Step 5/09 – Download and install the: Microsoft Azure AZCopy Tool.

The PST import process is implemented by using a command base utility named – Microsoft Azure AZCopy Tool

We will need to download and install the Microsoft Azure AZCopy Tool

The download link to the Microsoft Azure AZCopy Tool appears in the top part of the window of the Import files to Office 365 – upload file over a network.

Click on the Download tool link and install the tool.

Note – The Microsoft Azure AZCopy Tool will be installed in the following path -C:\Program Files (x86)\Microsoft SDKs\Azure\

In the following screenshot, we can see that the Microsoft Azure AZCopy Tool appears in the start menu under – Microsoft Azure.

Additional reading

Getting Started with the AzCopy Command-Line Utility

Step 6/09 – Create the required command syntax for the Microsoft Azure AZCopy Tool.

In this phase, we will “build” the required command syntax that will be used by the Microsoft Azure AZCopy Tool for “uploading” the PST file\s into the Office 365 storage.

At first look, the syntax of the command looks a little bit scary!

We will need to edit the example that appears in the article for customizing the parameters for our specific scenario.

The best practice is to copy the command example of a text editor such as notepad and edit the required parameters that will suite to our scenario.

An example of the required command syntax appears in the article – Office 365 Import Service

AzCopy.exe /Source:\\SERVER01\PSTshare1 /Dest:https://d1717df0c99e4157xyz520a.blob.core.windows.net/ingestiondata/SERVER01/PSTshareR1 /Destkey:bVqiKup0j7Bxik39vSN/zV3UveKHWs vmYb+NsvyoJs2Dhb8kOYIqmE2IPuC7uA7h3dTKJ1EmA0fWF3lPtBYtqA== /S /V: C:\PSTUpload\Uploadlog.log

We will need to update the existing command the example, in the following way:

1. The Source parameter

We will need to add the UNC path of the folder that we shared in the former step (Step 1/09 – Create a network share for storing the PST files).

In our scenario, the UNC path is:

AzCopy.exe /Source:\\SRV1\PSTshare1

2. The DST (destination parameter)

We will need to use a combination of the value that we got from the former step (Step 4/09 – Copy the value of the SECURE KEY and the SECURE URL and save it) of the SECURE URL + add the path to the folder that stores the PST file.

Pay attention that now we will not use the UNC naming convention, but instead, add the shared folder path using the “URL address” naming convention.

In our specific scenario, the value of the SECURE URL is – https://d1717df0c99e4157xyz520a.blob.core.windows.net/ingestiondata

The value of the shared folder is – /SRV01/PSTshare1

The combination of these two values is:

/Dest:https://d1717df0D99e4156xyz520a.blob.core.windows.net/ingestiondata/SERVER01/PSTshareR1

3. The Destkey value

The value of the key is the value that we save in the former step (Step 4/09 – Copy the value of the SECURE KEY and the SECURE URL and save it).

In our specific scenario, the value of the SECURE KEY is-

bVqiKup0j7Bxik39vSN/zV3UveKHWsvmYb+NsvyoJs2Dhb8kOYIqmE2IPuC7uA7h3dTKJ1EmA0fWF3lPtBYtqA==

The parameter that will include the secure key is – Destkey

/Destkey:bVqiKup0j7Bxik39vSN/zV3UveKHWsvmYb+NsvyoJs2Dhb8kOYIqmE2IPuC7uA7h3dTKJ1EmA0fWF3lPtBYtqA==

4. The log file path

The last parameter is the folder which will be used to contain the log file of the PST migration process.

In our specific scenario, we will save the log file in the Temp folder in C: drive and name the log file – Uploadlog.log.

/S /V:C:\TEMP\Uploadlog.log

This an example for the complete command syntax. In the following screenshot, we can see a presentation for each of the different parameters that we will need to update.

Additional reading

Getting Started with the AzCopy Command-Line Utility

Office 365 Import Service

Step 7/09 – Start the import process by using the Microsoft Azure AZCopy Tool.

In this phase, we will use the Microsoft Azure AZCopy Tool for “uploading” the PST file\s into the Office 365 storage, using the command syntax that we have prepared in the former step.

Technically, we can copy the command from the notepad and paste it into PowerShell console of the Microsoft Azure AZCopy Tool.

From my experience, we can experience a problem because – the command is very long and when we paste the command into the PowerShell console the execution of the command can fail because the issue of spaces in the command syntax, etc.

In case that you experience problems when using the copy and paste option, we can bypass this issue by executing the command by using a batch file.

To use a batch file, we will need to save the information in the notepad and save the file using a *. BAT file extension.

To activate the batch file, we will call the batch file from the Microsoft Azure AZCopy Tool PowerShell console.

In the following example, we run the command by using Batch file.

In our scenario, I have saved the text file as PST01.BAT in C: Temp folder.

Running the required import command in Microsoft Azure AZCopy Tool PowerShell console

Access the Microsoft Azure AZCopy Tool PowerShell console by using the start menu and access the Microsoft Azure folder.

The following PowerShell console appears.

To execute the batch file, we will type the batch file name.

In our example, we will call the batch file that is stored in the C:\TEMP folder.

In the following screenshot, we can see the results:

The command completes successfully.

1 file (PST file) was “transfer” to the Office 365 stores (the PST file that as exported from Outlook in phase – Step 2/10 – Export outlook data to PST file).

The information about the PST import process is saved in a log file. In the following screenshot, we can see we can see the information that was saved in the Log file.

Step 8/09 – Prepare the required CSV file (PST user mapping file).

Until now, we have to finish to “send” the PST file\s to the Office 365 storage.

In the next phase, we will need to use the Office 365 portal to complete the process by accessing a specific PST file that was saved in the Office 365 stores and then import the PST file\s into the Office 365 user mailbox.

To be able to “inform” the Office 365 portal about which of the PST files will be imported to the specific Office 365 user mailbox, we will need to use a CSV file.

In the following part, we will demonstrate a simple scenario in which we configure the CSV file to map a specific PST file to s specific user mailbox.

Note – there is an option to implement a more complicated scenario in which we import a couple of PST files into a specific Office 365 user, mailbox or a scenario in which we import the bulk of PST file into different Office 365 user mailboxes.

The CSV file structure includes the following parameters:

Workload – Office 365 service into which data will be imported. For email, use “Exchange”.

FilePath – the path of the folder that store the PST file\s. In our scenario the path is srv1/PSTshare1

Name – the PST file name. In our scenario the file name is –pst10.pst

Mailbox – the Exchange Online “destination mailbox”. In our scenario the destination mailbox name is – [email protected]

IsArchive – Whether or not to place the PST in the Online Archive:

If you want the PST to get imported into the primary mailbox, you can specify IsArchive as FALSE.

If you want the PST to get imported into the online archive, you can specify IsArchive as TRUE. This is the default value.

TargetRootFolder – this is the name of the folder that will be created in the user mailbox that will

In the following screenshot, we can see an example of the content of the CSV file.

In our specific scenario we use the following parameters:

The file path is: srv1/PSTshare1

Name – the name of the PST file is – pst

Mailbox – the PST file will be imported into the admin mailbox

Target root folder – the folder name that will be created and serve as a container for the PST file is – pst10

Note – You can download an example of the CSV file from the following link – xxxxx

note -Regarding the naming convention of the different parameters such as PST file name or the Target root folder, there is no specific instruction regarding the naming convention, but my recommendation is to “make it simple”. Don’t use the name with space, try to avoid from complicated name or non-standard characters and so on.

Phase 03#03

The compilation of the importing PST task, will be implemented by using the Office 365 admin portal.

Step 9/09 – Start the import PST process (Import job).

Login to the Office 365 portal and click on the Admin option

On the left, menu bar looks for the IMPORT menu.

Click on the plus icon and choose the option – Upload data over the network.

Choose the option boxes:

I‎’m done uploading my files

I have access to the mapping file

We will need to name the PST import job. In our specific scenario, we will name it as – admin-10

To add the CSV file, click on the plus sign and select the CSV file that was created in the former step (Step 8/09 – Prepare the required CSV file (PST user mapping file)).

In our specific scenario, the CSV file name is 01.csv

Check the option box – by checking this box you agree to the terms and the condition of the service

In the following screenshot, we can see the last screen which informs us that the “task job” is running.

In the following screenshot, we can see that the import job is running (import in progress).

When the import job complete, we can use the View detail’s option to get additional information about the job. For example, verify if the job complete successfully or a scenario in which the job didn’t complete successfully (complete with errors).

In the following screenshot, we can see the results: a new folder was created in the user mailbox named – PST10, which includes the content of the PST file.

  The former article in this series is:

Office 365 Import Service – Import PST into Office 365 user mailbox | Part 1#2

New Post has been published on http://o365info.com/office-365-import-service-import-pst-into-office-365-user-mailbox-part-1-of-2/

Office 365 Import Service – Import PST into Office 365 user mailbox | Part 1#2

In the current article, we will review an Office 365 service named: Office 365 Import Service, which enables us to import PST files into existing Exchange Online mailboxes. The Office 365 Import Service relates to two different types of scenarios:

Scenario 1 – ship drives to Microsoft. A scenario in which we store the PST file on a hard drive and ship the drive to Microsoft that will implement a procedure of importing the PST file to the required Exchange Online mailboxes.

Scenario 2 – import PST file from our network to a dedicated store located at Office 365 and later provide some instructions that we import the PST file that stored in the “cloud” to the required Exchange Online mailbox\s.

The current two article series, is dedicated to Scenario 2, which described as Import files into Office 365 through the network upload.

Office 365 Import Service | The article series

The article series include the following articles:

Office 365 Import Service – Import PST into Office 365 user mailbox | Part 1#2

Office 365 Import Service – Import PST into Office 365 user mailbox | Part 2#2

Table of content

Step 1/09 – Create a network share for storing the PST files.

Step 2/09 – Export outlook data to PST file.

Step 3/09 – Add the required Exchange Online permissions (assign the Mailbox Import Export admin role).

Step 4/09 – Copy the value of the SECURE KEY and the SECURE URL and save it.

Import files into Office 365 through a network upload

The process of Import files into Office 365 through the network upload includes a couple of steps and “first-time” configurations setting that we will review later on.

We can define two “major” steps that relate to the scenario of Import files into Office 365 through a network

Step 1 – copy the PST file\s from our local network to a dedicated store in Office 365.

In this step, we will need to export the information to a PST file and store the PST file\s on a network share.

Later on, we will need to use a tool named: Microsoft Azure AZCopy Tool that will help us to “upload” the PST file that are stored in our local network to the “cloud” (the Office 365 dedicated store that will be created for storing our PST files).

Step 2 – import the PST file\s to the required Exchange Online mailbox

After the PST, files are successfully copied to the Office 365 stores our next step is to import a specific PST file to a specific Exchange Online mailbox.

The import process is based on a CSV file that will use for “map” a specific PST file to a specific Exchange Online mailbox.

For example, we have imported to the cloud (Office 365) two PST files. A PST file named: John.pst + a PST file named: Alice.pst

We want to import the PST file name: John.pst into an Exchange Online mailbox of a user named: john.

To be able to complete this task, we will need a way to “tell” Office 365 that he will need to select the specific PST file (John. PST), look for an Exchange Online mailbox of a user named – John and import the content of PST file to John’s mailbox.

Implementing Import files into Office 365 through a network upload | Task list

The task of Implementing Import files into Office 365 through a network upload cab be a little confusing because in practice, it. Composed of a number of tasks and activities.

To be able to see the “big picture” I will display the general task list, and later, we will review in details each of the separated tasks.

Create a network share for storing the PST files.

Export outlook data to PST file

Copy the PST files in the network share.

Add the required Exchange Online permissions (assign the Mailbox Import Export admin role).

Copy the value of the SECURE KEY and the SECURE URL and save it.

Download and install the: Microsoft Azure AZCopy Tool.

Create the required command syntax for the Microsoft Azure AZCopy Tool based on the SECURE KEY and the SECURE URL value) and start the import process (waits until all the PST files are successfully uploaded to the cloud).

Prepare the required CSV file (PST user mapping file).

Login to Office 365 admin portal and start the import process (Import job).

Step 1/09 – Create a network share for storing the PST files.

In our scenario, we will create a network share on a server named – SRV1 and the folder name who will store the PST will be named – PSTshare1

The PSTshare1 folder will serve as a container for all the PST files that we want to upload to the cloud.

The “preparation” of the shared folder is based on two steps.

Share the folder.

Provide the required file permissions (NTFS permissions). Although the formal article doesn’t mention the need to assign file permission, from my experience if we don’t assign the file permission, the PST migration process failed.

1. Sharing the folder

We will need to share the folder because later, when we use the Microsoft Azure AZCopy Tool to import the PST file to the cloud, the command syntax will use the naming convention of UNC path (\\machinename\folder name)

  In the following screenshot, we can see the PSTshare1 folder that was created.

Right click on the PSTshare1 folder and choose properties.

Choose the sharing tab

Click on the Advanced Sharing

Add Everyone group and assign the Full control permission.

2. Provide the required file permissions (NTFS permissions).

In this step, we will assign the required permissions to the PSTshare1 folder.

Choose the Security tab

Click on the Edit… option

Click on the Add… option.

Add the Everyone group

Step 2/09 – Export outlook data to PST file.

Technically speaking, we can use any PST file that we have or get from our customers \users.

In the specific scenario, we will demonstrate how to export the PST file from Outlook client.

Choose the File menu and then choose the Open & export option.

Click on the import/Export option

Choose the – Export to a file

Choose – Outlook Data file [.pst]

In our specific scenario, we will export all of the mailbox content.

Choose the inbox icon and then – Next

In our specific scenario, we will save the PST file into the shared folder that was created and share din the former step – the PSTshare1 folder (we will name the PST file using the name pst10.pst)

In the following screenshot, we can see the PST file that was saved in the PSTshare1 folder

Step 3/09 – Add the required Exchange Online permissions (assign the Mailbox Import Export admin role).

To be able to use the PST migration option, we will need to assign the required permission to the user account that will perform the migration task.

In the Exchange Online admin center, choose the permissions menu and admin roles

Click on the plus icon and double-click on the – Compliance Management role.

Choose the permission – Mailbox Import Export

Choose the account name who will perform the PST migration.

In the following screenshot, we can see the results-

Under the Roles section, we can see that the Mailbox Import Export

Under the Members section, we can see that the admin users appear.

Phase 02#03

Before we begin with the instructions, it’s important to understand the logic of this phase.

The PST migration process is based on a concept in which we upload and store the PST file of “Office 365 storage” and from this storage, import the data (the PST files) into specific Exchange Online mailboxes.

The “dedicated Office 365 storage” that will be created for use is represented by a dedicated URL address and unique Key (I assume that the Key serves for security purpose for encrypting the data on the Office 365 storages).

The dedicated URL address described as – SECURE URL

The dedicated Key described as – SECURE KEY

As far as I know, the value of the SECURE URL and the SECURE KEY will be created as a one-time process and will serve, as for all the future tasks of importing PST files.

For this reason, it’s recommended to save these values for future use.

In the following step, we will “jump” into the PST migration step because when we initialize this step in the first time, the values of the SECURE URL and the SECURE KEY will be created.

Later on, we will use this value for the command syntax that will be used by the Microsoft Azure AZCopy Tool that will help us to “upload” the PST file that are stored in our local network to the “cloud” (the Office 365 dedicated store that will be created for storing our PST files).

Phase 01#03

Step 4/09 – Copy the value of the SECURE KEY and the SECURE URL and save it.

Login to the Office 365 portal and click on the Admin option

On the left, menu bar choose the IMPORT menu.

Click on the plus icon and choose the option – Upload data over the network

In the following screenshot, we can see that there are a couple of options. In the current phase, we are interested only in the values of the SECURE URL and the SECURE KEY

Under the section of – copy the secure storage account key, click on the Show key option and save the value that appears in notepad for later use.

In the following screenshot, we can see an example of the value of the SECURE KEY.

Under the section of – copy the secure network upload URL, click on the Show URL option and save the value that appears in notepad for later use.

n the following screenshot, we can see an example of the value of the Secure URL.

An additional option that we can use for displaying the values of the SECURE URL and the SECURE KEY is by choosing the “Key icon”

The next article is:

Office 365 Import Service – Import PST into Office 365 user mailbox | Part 2#2