Exporting entites from 3.0 and import it to Titan

Is it possible to export entities from CRM 3.0 and import them to Titan?
If it is possible... how will I do that?

CList
Sun Feb 10 15:00:02 CST 2008

The SDK documentation is pretty clear about it:

"You can import and export only between systems that are running the same
version of Microsoft Dynamics CRM. "

http://msdn2.microsoft.com/en-us/library/cc151166.aspx

However, I'd like to get some more clarification on this from the Dynamics
team. Obviously they have a tool for upgrading existing customizations, and
it would be nice if that tool could be run "standalone" on a
customizations.xml file from CRM 3 to upgrade it to CRM 4 format.

Looking at xml export files from each version of CRM, I see quite a few
differences, and writing a bit of C# to do the conversion would be
non-trivial as you'd have to do things like go to the metabase tables to get
GUIDs for the AttributeType, etc., still, it doesn't seem impossible.

Cheers,
CList


"Martin" wrote:
> Is it possible to export entities from CRM 3.0 and import them to Titan?
> If it is possible... how will I do that?

Peter
Sun Feb 10 16:32:27 CST 2008

It's called an inplace upgrade from CRM3.0 to CRM4.0. in a dev/test
environment - another system or a virtualpc etc


"CList" <CList@discussions.microsoft.com> wrote in message
news:C0277015-A315-4808-A2B0-5DBC92636CD8@microsoft.com...
> The SDK documentation is pretty clear about it:
>
> "You can import and export only between systems that are running the same
> version of Microsoft Dynamics CRM. "
>
> http://msdn2.microsoft.com/en-us/library/cc151166.aspx
>
> However, I'd like to get some more clarification on this from the Dynamics
> team. Obviously they have a tool for upgrading existing customizations,
> and
> it would be nice if that tool could be run "standalone" on a
> customizations.xml file from CRM 3 to upgrade it to CRM 4 format.
>
> Looking at xml export files from each version of CRM, I see quite a few
> differences, and writing a bit of C# to do the conversion would be
> non-trivial as you'd have to do things like go to the metabase tables to
> get
> GUIDs for the AttributeType, etc., still, it doesn't seem impossible.
>
> Cheers,
> CList
>
>
> "Martin" wrote:
>> Is it possible to export entities from CRM 3.0 and import them to Titan?
>> If it is possible... how will I do that?

mscrmexpert
Mon Feb 11 04:20:01 CST 2008

Import CRM 3 customization to CRM 4 is not possible and supported. You have
to do upgrade and that will work for you.

For more see MS CRM 4.0 implementation guide

--
Regards,
Imran
MS CRM Certified Professional


http://microsoftcrm3.blogspot.com

Chat with me on MSN / Gmail / Skype : ID Is :.. mscrmexpert@gmail.com



"Martin" wrote:

> Is it possible to export entities from CRM 3.0 and import them to Titan?
> If it is possible... how will I do that?

Scott
Mon Feb 11 22:16:42 CST 2008

On Feb 11, 4:20=A0am, Imran-mscrmexpert <mscrmexp...@gmail.com> wrote:
> Import CRM 3 customization to CRM 4 is not possible and supported. You hav=
e
> to do upgrade and that will work for you.
>
> For more see MS CRM 4.0 implementation guide
>
> --
> Regards,
> Imran
> MS CRM Certified Professional
>
> http://microsoftcrm3.blogspot.com
>
> Chat with me on MSN / Gmail / Skype : ID Is :.. mscrmexp...@gmail.com
>
>
>
> "Martin" wrote:
> > Is it possible to export entities from CRM 3.0 and import them to Titan?=

> > If it is possible... how will I do that?- Hide quoted text -
>
> - Show quoted text -

Peter and Imran,

I think what clist is asking for is reasonable. The upgrade that MS
has put in place puts a lot of overhead on testing the upgrade
process. Having to implement a test environment and redeploy is a
pain and could have been done a little bit better. All of the tools,
including the one that clist is referring to exist, they have just not
been broken out seperately. Seeing that CRM has been customized by
many to the nth degree, it would be nice to have some additional tools
to test our customizations without having to duplicate the entire
environment first. Most of the customizations reside in the database
and the scripts that run during the upgrade process could have been
seperated from the rest of the process, this would have been good for
isolating and testing seperately without having to use the
redeployment wizard to build a test environment.

Scott
www.easiintl.com