Migrate Exchange 2003 Public Folders to Exchange 2013
-
I'm going to hugely unhelpful.... but Ugghhh Public Folders suck...
-
@coliver said:
I'm going to hugely unhelpful.... but Ugghhh Public Folders suck...
Yeah, as does going from Exchange 2003 to 2013...
-
Question: If I export the public folder to a PST using something like Outlook 2010, can I import that directly into Exchange 2013 from a PST?
-
Pinging @dengelhardt and @PSX_Defector on this one!
-
Now to be slightly more helpful. How is the public folder laid out? Do you have access to Outlook attached to this Exchange server? If the folder layout is relatively simple (as in just a contact list) you could migrate the contents of the folder to Outlook, do the upgrade, recreate the public folder, then move the contacts over to the appropriate place.
This is basically what I did with out move to O365, you will have to re-add most of the permissions though.
-
@coliver said:
Now to be slightly more helpful. How is the public folder laid out? Do you have access to Outlook attached to this Exchange server? If the folder layout is relatively simple (as in just a contact list) you could migrate the contents of the folder to Outlook, do the upgrade, recreate the public folder, then move the contacts over to the appropriate place.
This is basically what I did with out move to O365, you will have to re-add most of the permissions though.
This Public Folder has a massive amount of stuff in it, although I can't tell you exactly what.
-
@thanksaj said:
@coliver said:
Now to be slightly more helpful. How is the public folder laid out? Do you have access to Outlook attached to this Exchange server? If the folder layout is relatively simple (as in just a contact list) you could migrate the contents of the folder to Outlook, do the upgrade, recreate the public folder, then move the contacts over to the appropriate place.
This is basically what I did with out move to O365, you will have to re-add most of the permissions though.
This Public Folder has a massive amount of stuff in it, although I can't tell you exactly what.
Understood then this solution probably wouldn't be the best.
-
It's been a few years, but I migrated our Public Folders from 2003 to 2010 by adding the 2010 Exchange server as an additional replication partner. Once the folders were completely moved over, I updated the public folder location using PowerShell (there's a lot of documentation out there that goes over this process) and then removed the old Exchange server from the Public Folder synchronization partners.
I'd have to look it up again, but it wasn't terribly difficult.
-
Something like this:
http://www.petenetlive.com/KB/Article/0000426.htm
Again it's been awhile, and I think there are a few different ways to do what you're trying to do.
-
@Rob-Dunn said:
It's been a few years, but I migrated our Public Folders from 2003 to 2010 by adding the 2010 Exchange server as an additional replication partner. Once the folders were completely moved over, I updated the public folder location using PowerShell (there's a lot of documentation out there that goes over this process) and then removed the old Exchange server from the Public Folder synchronization partners.
I'd have to look it up again, but it wasn't terribly difficult.
That's what I've been reading is that to go from Exchange 2003 to 2013, you have to do a dual-migration. You have to migrate the public folders to Exchange 2010 first and then you can go to Exchange 2013. If I just export it as a PST, can I import it directly into Exchange 2013?
-
I personally wouldn't do this - I would let Exchange do it naturally, you might run into wonky permissions issues and cause yourself more headaches in the future.
-
@Rob-Dunn said:
I personally wouldn't do this - I would let Exchange do it naturally, you might run into wonky permissions issues and cause yourself more headaches in the future.
This thing can't get more screwed up than it has been...
-
Other than the 2003->2007->2010 method, the only thing I can suggest is migrating OUT of public folders into Sharepoint.
http://www.quest.com/migration-suite-for-sharepoint/
Although I haven't tried it in a while, maybe the Quest tools would be better for this situation anyways. 2003 to 2010 is a large infrastructure change, lots of AD prep and massive backend changes. Assuming since they are still using 2003 they are probably on a 2003 schema, so maybe using a better tool would be better for them.
http://software.dell.com/products/migration-manager-for-exchange/
-
@PSX_Defector said:
Other than the 2003->2007->2010 method, the only thing I can suggest is migrating OUT of public folders into Sharepoint.
http://www.quest.com/migration-suite-for-sharepoint/
Although I haven't tried it in a while, maybe the Quest tools would be better for this situation anyways. 2003 to 2010 is a large infrastructure change, lots of AD prep and massive backend changes. Assuming since they are still using 2003 they are probably on a 2003 schema, so maybe using a better tool would be better for them.
http://software.dell.com/products/migration-manager-for-exchange/
We've already created a new domain for them and they are using the new Exchange server. We had exported all their mailboxes to PSTs and have imported them into the new Exchange by way of Outlook (it's the only way we could get it to work). All that's left is this one Public Folder on the old Exchange server.
-
@thanksaj said:
@PSX_Defector said:
Other than the 2003->2007->2010 method, the only thing I can suggest is migrating OUT of public folders into Sharepoint.
http://www.quest.com/migration-suite-for-sharepoint/
Although I haven't tried it in a while, maybe the Quest tools would be better for this situation anyways. 2003 to 2010 is a large infrastructure change, lots of AD prep and massive backend changes. Assuming since they are still using 2003 they are probably on a 2003 schema, so maybe using a better tool would be better for them.
http://software.dell.com/products/migration-manager-for-exchange/
We've already created a new domain for them and they are using the new Exchange server. We had exported all their mailboxes to PSTs and have imported them into the new Exchange by way of Outlook (it's the only way we could get it to work). All that's left is this one Public Folder on the old Exchange server.
I should add the old DC was Server 2003 R2 as well.
-
You should be able to export the Public Folders into a mailbox pst file and then import them into a mailbox in Exchange 2013. Theoretically that will work according to Microsoft.
-
@dengelhardt said:
You should be able to export the Public Folders into a mailbox pst file and then import them into a mailbox in Exchange 2013. Theoretically that will work according to Microsoft.
It worked with the user mailboxes. Hopefully it'll work with the Public Folder.
-
@thanksaj
I didn't realize there was a new domain...that would explain why you're not doing coexistence, which is what most normal installations would follow. Not saying it couldn't be done, I mean you could create a domain trust and go that route, but things are a bit more clear now.
Just be careful...you know, you should reach out to Jay6111 in the SW forums, he's awesome with Exchange and might have some good tips.
-
Here are few articles for your reference:
How to Move Public Folder from Exchange 2003 to Exchagne 2010
Migrate public folders to Exchange 2013 from previous versions
https://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
-
Why are you posting on a thread that is more than 2 years old?
