How to safely remove 2007 legacy Public folders during 2013 co-existence

Dear Experts

We've been having many issues during our migration for Exchange 2007 SP3 CU14 to Exchange 2013 CU6 with interim update to resolve the DB dismounting and EAS proxy issues.

Our environment consists of a small organisation, ie one 2007 exchange and one Exchange 2013.

I need to plan for the removal of the legacy public folders, of which there is only one in use. I will even move this to a shared mailbox rather than worry about migrating to a modern PF. Given that there is only one PF in use could I simply:

1) Delete the legacy PF's after checking the important one is OK as a shared mailbox
2) Remove the Public folder database using these guidlines:

http://technet.microsoft.com/en-us/library/aa998329(v=exchg.80).aspx

3) Finally go ahead and decommission Exchange 2007

With all the research I have done many articles seem to be older than regarding CU6 era information or talking about migrating them first which I don't think is necessary in our case.
Assist-NetopaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

VB ITSSpecialist ConsultantCommented:
If you only have the one Public Folder that needs to be migrated then I don't see any real issues with the above steps. You can even look at using Outlook to export the contents of the Public Folders to a PST file, then import them into the new PF mailbox in Exchange 2013.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Assist-NetopaAuthor Commented:
Thanks, I guess that's what I thought it's just there have been so many issues with Exchange, whether that's hotfixes, permissions, split dns, activesync, EAS, proxying ... don't know what to believe any longer..

Not even going to use a PF Database/Mailbox just a normal mailbox as you'd first have to remove legacy public folders. Just going to try and K.I.S.S
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.