We have an instance of CRM 3.0 running on Small Business Server. We
also have a new instance of CRM 4.0 running on a different, standalone
server. We want to migrate our data from 3.0 to 4.0, but the only
path that appears obvious is via an upgrade, which this isn't, as it's
on a different server. For obvious reasons we would prefer to avoid a
brute force approach (using DTS or, rather Visual Studio Integration
Services - can anyone point us in the right direction?

Thanks

Edward

I am sure you have heard the name of scribe but can you tell about the
data . What entities are having data ? Might be it is easy to make
CSV and import the data to current CRM .

OR you can move the databases into your current domain and then re-
install the server while pointing to the existing databases (you need
to create the CRM security group ) at active directory . It will easy
to upgrade to CRM4.0 .

/Aamir

Can you not Backup/restore the DB onto the new server? (you would have to
install CRM 3.0 on the new server and then run the upgrade)

Is your new CRM Server in a different domain? (then you just have to run the
redeployment Wizard before running the 3.0 install, then the upgrade

Am I missing something else?

--
Grizz


"teddysnips@hotmail.com" wrote:

We recently did this, moving from SQL2000/CRM3 to SQL2005/CRM4 on a new
server. In short,

1. Stop all the CRM Services
2. Backup Database
3. Restore Database to New Server
4 Run Redeployment Wizard, be sure you have used a new OU for the CRM OU.
This keeps your existing stuff intact in case your upgrade fails.
5. Pick the same users instead of mapping new users.
6. Install CRM 3.0
7. Import customizations
8. Intall CRM 4.0

Be sure and reference the CRM3.0 Redeployment Guide and the Implementing CRM
4.0 Guide for further info.

We did this upgrade three times before marking out a weekend and switching
the business over.

Lots of issues with 4.0 client if the 3.0 client was on the machine though.
Be sure and uninstall old client. Deleting outlook.cmd helped sometime,
entire new profiles needed other times



"GrizzlyTech" wrote:

Hi Nangard,

I am glad I came across this post, coz it is exactly what I need to complete
and have been having some trouble completing this. I wanted to clarify/expand
on some of the steps you have put in your post and hopefully get a more
detailed migration plan. My scenario is CRM 3 on SQL 2000 SP4 to be migrated
to CRM 4 on SQL 2005 SP1 (2005 is on an instance, as opposed to previous
setup, may also be able to upgrade to SP2, but this instance is being used by
other databases).

Following your steps from 1 to 8, I have listed some questions and areas
requiring some further input.

1 & 2 - All good here...
3 - I assume you restore the "CompanyName_METABASE" and "CompanyName_MSCRM"
databased to the SQL 2005 server into my instance on the SQL 2005 server. -
All cool here if this is the case.
4 - I then ran the CRM Deployment Manager installed with CRM 3 to configure
the SQL Database server. I am going to assume this is different to what you
have stated as being the "Redeployment wizard", coz there is no place to
select a new OU etc.
5 - Have no idea what you are referring to here, I suppose this is because I
am not using the redeployment wizard?
6, 7 & 8 - Not following why CRM 3 is installed again and imported
customisations, when CRM 3 server already exists and working on the new SQL
server by this stage?

I figured the best approach would be to migrate the databases to the new
server and then complete an upgrade to CRM 4, as I read somewhere that CRM
needs SQL 2005 to work.

I would prefer to re-install CRM 4 on a new server using the existing data.
This way I have a fallback and I have a fresh install...but I will need to
ensure customisations and data remains intact.

I was not able to find a copy of the CRM 3 Redeployment guide you referred
to as well? I have also seen a number of recommended methods for moving from
CRM 3 to CRM 4 and all seem different. I need an approach that has fail safes
and can easily roll back in event of failure etc.

Any assistance would be appreciated.

Thanks in advance.
Adrian



"Nangard" wrote:

Hello Kit,

Just went back through my notes on this. Clearly they were written just for
me or I would just cut and paste them in.

3. Your restore both of your databases to SQL. When CRM 4.0 runs, it will
convert your Company Name_Metabase into the multitenancy database and make
whatever conversions it needs on your MSCRM database.
4. I think it is the CRM install that asks you for the OU that you need?
Make a different OU in AD for this so you don't screw up your existing
install.
5. THe CRM 3.0 install is going to ask you where to put the CRM AD info.
Put it in the New OU.
6. You need to follow the instructions in the Redeploying Microsoft CRM 3.0
whitepaper regardig this. I don't know where I got it, but that is its exact
title. I did a quick search and it did not pull up .

Yes, you have to upgrade the existing install. I would encourage you to
build a virtual server and test all this stuff out and write down a
methodology that works for you so that you will be successful when you want
to transition.


"KIT_Adrian" wrote:

Thanks Nangard. I was just wanting to save myself some time and get some
feedback from others who have done this. It really should be documented
better...or maybe I am not seeing the right documents. I will ahve to try
this from scratch in a virtual environment and compelte all possible methods
that work and see what happens.

Thanks for your assistance.

Regards,
Adrian

"Nangard" wrote:

Your welcome,

BTW, The CRM 3.0 redeployment paper is on the CRM media under the
redeployment tools folder. Get that PDF. It will help.


I think it is really important for you to get a migration on a test
platform functional before you try to move the company over. You will have
enough problems with the change as is. Best to eliminate what you can
control.

I know that I migrated 3 times before I moved the company. By the third
time, it was fast and familiar, but I still had unforseen issues with the
client piece, installtion on our citrix servers and other regular stuff that
crops up.

Good luck

"KIT_Adrian" wrote:

Just to feed in here I'm currently doing this myself with vaired success.
Had wanted to test the upgrade on eitehr a virtual machine or a standalone
clone of our current server but after much fighting wasn't abel to get a
clone of our server to run in anything but safe mode. Too many hardware
differences I expect.

So had no option but to go for it live on the main server one weekend.
So Acronis images made of all drives and tape backup run as well.

Backed up CRM database (plus did customisation and workflow exports)
Unitsalled CRM 3.0
Uninstalled C360 wordmailmerge

SBS 2003 SP2 upgraded to SBS 2003 R2 (with SQL2005)
Much fun getting reporting services to work!
Re-attached CRM and other databases (many problems here with SQL2005 and
permissions etc wasn't across how different SQl2005 is!)
Re-installed CRM 3.0 and chose to use existsing database and that connected
fine.

Server had quite a few issues with the R2 upgrade and my mistake was to go
ahead with CRM 4.0 upgrade. I should have held fire at that point.
CRM 4.0 upgrade seemed to work fine and I even half saw the CRM 4.0 opening
webscreen but I has issues connecting with the data. After many hours and
becoming aware that the serve rhad otehr issues I uninstalled CRM 4.0
re-installed CRM 3.0 and have settled at that for now.

Server is almost straight now and I'm looking at the next step to have
another shot at the CRM upgrade.

One issue I do have currently is that we went to Office 2003 a week or so
before my upgrades in prep for CRM 4.0 (that doesn't support Office 2002)
and taht ahs broken our ability to do a quick campaign mail merge. I know
this is a client issue as I have an old workstation that still has office
2002 and that still mail merges fine.

It maybe related to being unable to install the CRM 3.0 rollup 3 on the
server. it keeps insisting that rollup 2 need as installing but it's already
installed.

"Nangard" <Nangard@discussions.microsoft.com> wrote in message
news:5761F0C4-9D0C-4A10-A83C-57C4820B1686@microsoft.com...

Pat,

The way to setup a test migration environment is to use Virtual Servers ( I
used Microsoft Virtual Server), and go through redeploying to a new server
using the redeployment guide. Then you upgraded and test on that server.



"Pat Horridge" wrote:

Yes I'm doing that now as well.
Ideally I prefer to take a snapshhot of my system and restore that to a
virtual server and test on that so I can be sure I'm taking everyting into
account.
But I really struggle to restore an image of my server to a virtual server
and have it run.

But in the mean time I'm testing restoring my CRM data to a vanilla server
2003 setup and then test the upgrade route.


"Nangard" <Nangard@discussions.microsoft.com> wrote in message
news:A76056E5-7F9F-4764-90F9-6328F9A0949A@microsoft.com...