1. You need to first start with WSS 2.0, upgrade to WSS 3.0, then upgrade to
MOSS 20072. The top level site will be your top level site from your
original site. The template will not be upgraded so the look and feel after
you finish your upgrade will look just like WSS 2.0 on the first pages. As
you navigate into lists and the settings then you'll be seeing the new WSS
3.0/MOSS style pages. You can reset the site template which will then give
you the look and feel of WSS 3.0 all the way through the site.
3. We haven't tested the My Site migration  yet, so I don't know about that.

If you do a search on Microsofts site for Sharepoint 3.0 upgrade you'll find
all the information on pre-requisites, planning and post upgrade steps for
upgrading. From our experiences here's a few of the gotchas that you might
have an issue with.

1. Make sure that you have patched the WSS 2.0 to the same level as the
original site. Just about everyone has to install the DST patch before they
can do a migration.
2. After the upgrade runs, it will display the job status page and only one
task will show. REFRESH and don't continue until you have about 4 or 5 jobs
(can't remember the exact number) and the progress on all of them show 100%.
The first time we tried an upgrade, it looked like it was finished but it
actually hadn't finished the jobs and it broke the upgrade.
3. Any customizations will effect how the look and feel of the final results
of the upgrade. Any customized pages could cause an issue with how the site
looks. We had one site that had a customization from Front Page and it had
some unusual layouts and colors. Resetting both the Site Template and the
Theme fixed the issues and the site looked fine then.

Thanks for Valuable info.
But I am looking for Contenet DB Migration type
is this steps also require for it to istall SPS 2003 on New Box where i am
going to migrate.

I have done this a few times now:

1. Install SharePoint 2007 Portal Server (MOSS) in the new
machine.

Although Microsoft recommends a different Web Service for MySites, my
experience tells that you should install MySites in the same Web
Service as the Portal.

2. Install WSS 3.0 SP1 and after MOSS SP1

3. Delete MOSS content  Database (created with the Web Service):
stsadm –o deletecontentdb –url http://intranet_name –databasename
MOSS_Content_DB –databaseserver SQL_server_name

4. Run prescan.exe on your SharePoint 2003 and correct eventual
errors and warnings.

5. Perform a SharePoint 2003 Content Database Backup

6. Restore the SharePoint 2003 Database to a new name (the name
you want for the final database, like Intranet_Content_DB). I am
assuming that you will use the same SQL Server. If not, restore the
Database to the new SQL Server.

7. On your MOSS machine do: stsadm –o addcontentdb –url
http://intranet_name –databasename Intranet_Content_DB –
databaseserver SQL_server_name

8. Go to "MOSS Central Admin -> SharePoint Web Application
Management -> Define managed paths": create a path "mysite"
with "explicit inclusion" and create a path "personal" with "wildcard
inclusion"

9. On "MOSS Central Admin -> SharePoint Site Management ->
Create site collection", create a site collection with the name you
want but on "Web Site Address" chose http://intranet_name/mysite
and "Template Selection" choose Enterprise -> My Site Host.

10. Go to "Shared Services Admin -> User Profiles and My Sites ->
My Site settings" and write on "Personal site provider":
http://Intranet_name/mysite and in "Personal site
location": "personal".


With these steps you will have your MOSS installation working with
your "MySites" with each personal site under
http://Intranet_name/personal path.

Beware that all your existing TeamSites in SharePoint 2003 will be
site collections placed in MOSS under http://intranet_name/sites.
They will NOT appear under "Site Actions -> Manage Content and
Structure".

All your Portal Areas in SharePoint 2003 will be Sub-Sites from your
Portal (intranet) on your MOSS installation.

11. Some of the imported sites will automatically have a MOSS
look and feel. Some (the customized ones) will remain with the
SharePoint 2003 look. Go to "Site Actions -> Site Settings -> Modify
all site settings" and under "Look and Feel" select "Reset to site
definition" if you want your sites to look new (I recommend that).


12. You will always have to dome some work by hand. Like
deleting/changing Web Parts that that stopped working. You also have
to re-create and re-assign all your audiences.


Most off the work is done automatically and works pretty good (that's
what I
think. Well, at least for the work I was expecting to have and
didn't).

I will work for this steps on staging server
The content  database is also having top level sites
so will this restore the top level site using the same steps?

Yes, this will restore everything you have on SharePoint 2003.

No need to thank. I've just did to you what I would like to have found
sometime ago when I had the same droughts you have. This would have
saved me lots of work hours.

Just had this doubt after replying to you: by "top level sites" you
mean they are on different content  DB's ? or are they in the same DB?

Any way: if they are on the same DB, just do as I described. If they
are in different DB's just repeat the "stsadm –o addcontentdb" as many
times as needed. Remember that the DB that contains the Portal must
always be the first one!

By the way: what nationality are you?

Ok, No I have only one content  DB.
i think it will work as per u r given stpes.
One more question about portal home page
Because in SPS 2003 Portal home page is different than other wss top level
site
I just finish MOSS setup and i found that after creating web application i
created top level site.
but when i access the web application is shows me blank but i can access the
other top level created site.
the URL like SPS 2003 we get portal home page at following URL

eg. http://<Machine <http://%3cmachine/> name>/Default.aspx

in MOSS this is not workkng any suggession ?