Home » Topic » Microsoft Exchange Server Migration from 2007 to 2016

Microsoft Exchange Server Migration from 2007 to 2016

Kerry Morris ~ Modified: April 26th, 2016 ~ ~ 1 Minute Reading

Home › Forums › Microsoft Exchange Server Migration from 2007 to 2016

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • April 25, 2016 at 5:17 am #1972 Score: 0
    Kerry Morris
    Moderator
    34 pts

    Hi Experts,

    Please help me to Migrate from Exchange Server 2007 to 2016. I have been thinking about it since last two months but I am not sure about downtime and complete migration and stepwise migration and migration like conversion of EDB file to PST and then import that PST into Other Newly installed server.

    I am confused in all these therms and I am unable to choose any one for Migration. Because I found all migration steps bit complicated.

    So, please tell that which one is better in which condition and what will be downtime during migration and all other information.

    I will be appreciated for that.

    Thanks in Advance.

    April 26, 2016 at 12:28 pm #1982 Score: 0
    Henry Davidson
    Moderator
    31 pts

    Hi Kerry,

    There are two ways of migration from Exchange 2007 to 2016.

    First you can go by Step wise migration. In this method there will be no downtime.

    Second, You can Export Exchange Database (EDB) to PST and then install new Exchange and then Import PST file to Newly installed Exchange Server. But in this method there will be downtime of Exchange Server till the time you won’t Import PST file.

    April 27, 2016 at 7:17 am #1985 Score: 0
    Dexter Morgan
    Moderator
    38 pts

    You can also migrate by exporting Exchange database to Outlook PST file using Get-Mailbox -Database [server]\FirstStorageGroup\MailboxDatabaseName | Export-Mailbox
    -PSTFolderPath [\\path\to\folder]     command in Exchange Server 2007. Then import PST file to Exchange Server using New-MailboxImportRequest –filepath \\ServerName\SharedFolder\PSTfile.pst -mailbox MailboxName Command in Exchange Server 2016.
    Run all commands in PowerShell or Exchange Management Shell.

    If above command fails to export then you have to use any third party tool to convert Exchange 2007 Mailbox to PST file format. Then easily import PST file to Exchange 2016 using above import command.

    Don’t forget to take backup first before going for any solution.

    Regards
    Dexter

    April 28, 2016 at 12:16 pm #1995 Score: 0
    Kerry Morris
    Moderator
    34 pts

    Thanks Dexter and Henry for replying

    Export Exchange 2007 to PST and then Import PST to Exchange 2016 is good. But I am very curious for my data so I don’t want to do something which may lead to data corruption.

    I did a lot of research about it and found that there is not such way to migrate 2007 to 2016 directly. But we can migrate by converting EDB file to PST and then import into newly installed exchange server.

    Is there any other way to perform migration? Please tell me any other solution for migration if possible.

    I will be appreciated for that.

    April 30, 2016 at 11:39 am #1999 Score: 0
    Henry Davidson
    Moderator
    31 pts

    You can follow step wise technique for migration of database from exchange 2007 to 2016.
    Using step wise migration you have to first migrate from Exchange Server 2007 to 2010 and then exchange 2010 to 2016 migration is possible.

    May 2, 2016 at 9:29 am #2010 Score: 0
    Kerry Morris
    Moderator
    34 pts

    Hi Henry,
    I checked the link for exchange 2010 to 2016 migration. Which was described very well, but before proceeding for exchange 2010 to 2016 migration i have to go for exchange 2007 to 2010 migration.

    So, Please tell me about any trusted and verified solution for exchange 2007 to 2010 migration.

    May 6, 2016 at 9:18 am #2034 Score: 0
    Henry Davidson
    Moderator
    31 pts

    Hi Kerry,

    You can follow this link for migration from 2007 to 2016.

  • Author
    Posts
Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.