Can any one reply to this question. I also need to do the same thing, in my
company.

I would recommend taking some time  to properly  assess your organization
to clearly identify your business requirements. Next, identify the
features of SharePoint that would meet those requirements, out of the
box and write a deployment plan.

What that does for you is allow you to generate a proof of concept,
maybe in a virtual environment. Also, it would allow you to build  out a
test environment on your hardware.

I am taking a stab here and assuming that you have a support agreement
with Microsoft. If so, you have the Software Assurance package for
Volume License
<www.microsoft.com/.../packagedservices.mspx>" target="_blank" rel="nofollow">www.microsoft.com/.../packagedservices.mspx>
. I have provided you with a brief description of the framework and a
url.

www.microsoft.com/.../packagedservices.mspx
<www.microsoft.com/.../packagedservices.mspx>" target="_blank" rel="nofollow">www.microsoft.com/.../packagedservices.mspx>

SharePoint Deployment Planning Services
SharePoint Deployment Planning Services (SDPS) is designed to help your
organization plan an effective deployment of Microsoft Office SharePoint
Server. Your consultant shares best practices, analyzes your
organizational environment, and provides tools and services to help you
optimize the effectiveness of the Office SharePoint Service core
capabilities, help lower the cost of deployment, and help improve the
productivity of your organization. The number of engagement days is 1,
3, 5, 10, or 15, as determined by your Software Assurance coverage.


In response to your question  for best practices  and hands on experience.
I can testify to the fact that this framework works. If you need a
recommendation for a partner, ping me and I can point you in the right
direction. I hope that this helps.

We are still working through this but will be using programmers to
write scripts that will gather some metadata based on folder
structure while some will be gathered through Microsoft properties
fields. We will still have to manually look at some data and tell
users that some items  may not be 100% accurate. We also implemented
Coveo search  engine which allows us to give our users  the capability
to "weed out" any items that are not relevant during their searches.
As we present our new Intranet - we're making it a point to stress
that old info may not be properly  tagged.

So far.... that's the best we've come up with.