locked
Ignoring fields during Data Import RRS feed

  • Question

  • Hi...
     
    I am migrating the data from 3.0 to 4.0 by exporting and importing the csv files using data import wizard.

    while importing it is ignoring some of the fields like status, status reason, created by, modified by, modified on for automatic data map or for the new data map created by us.
     
    It is assigning 
     New or Open for Status, Status reason
     Present date for Modified On and
     Current logged in user for Created By, Modified By

    I tried to import the Closed Leads in 3.0 version, but the status is being set to New in 4.0 and hence coming under the Open Leads.

    But I want the original values present in 3.0 version.

    How can import this data with all the original values associated with the records.


    Thanks...

    Sunday, February 8, 2009 2:09 PM

All replies

  • The import tool will ignore those fields.  You can try using the Data Migration Manager and see if you can import closed records through that tool.  If that does not work, you will need to use the SDK to develop a solution or you can use Scribe which is a fairly inexpensive solution but will take a little bit of training to learn to use the tool.  Below are links to the SDK and Scribe if you want to look into those solutions.  I also included a link to the DMM.

    I know you probably realize that the upgrade process will upgrade your database so you don't have to import records.  I understand that you were probably not able to take that approach. 

    DMM

    http://www.microsoft.com/downloads/details.aspx?FamilyID=6766880a-da8f-4336-a278-9a5367eb79ca&displaylang=en

    SDK

    http://msdn.microsoft.com/en-us/library/bb928212.aspx

    Scribe

    www.scribesoft.com

    Best Regards, Donna
    Sunday, February 8, 2009 2:46 PM
  • I've worked around this in the past by populating an additional field with an identifying value and then modifying the records once they are in CRM, isolating them with the identifying value. This is only good for up to a few thousand records as you can only update 250 at a time. For a more robust solution, Donna's suggestions are the way to go.

    Leon Tribe
    Want to hear me talk about all things CRM? Check out my blog
    http://leontribe.blogspot.com/
    Sunday, February 8, 2009 8:40 PM
  • Thank you all for your solutions...

    @Leon,

    I tried on populating an additional field with an identifying value. But the problem here is Created By,Modified By, Status are ReadOnly values.
    So, I am unable to modify them. Is there any other way to set the original values?


    @Donna,

    Upgrading 3.0 to 4.0 means do we need to install 3.0 version and upgrading it?
    If so, we already installed 4.0 version. So any other solutions?



    -Thanks.
    Monday, February 9, 2009 5:58 AM
  • Short of some unsupported SQL updates to the tables, or the tools suggested by Donna, I'm out of suggestions.

    Leon Tribe

    Want to hear me talk about all things CRM? Check out my blog

    http://leontribe.blogspot.com/
    Monday, February 9, 2009 12:56 PM
  •  @Donna,

    Upgrading 3.0 to 4.0 means do we need to install 3.0 version and upgrading it?
    If so, we already installed 4.0 version. So any other solutions?

    What I meant by the above was that when you upgraded from 3.0 to 4.0 you could have upgraded the database as well which would eliminate the need to import the data from 3.0 to 4.0.  I assume you have reasons for not taking that path.

    Here are some potential solutions.

    DMM

    http://www.microsoft.com/downloads/details.aspx?FamilyID=6766880a-da8f-4336-a278-9a5367eb79ca&displaylang=en

    SDK

    http://msdn.microsoft.com/en-us/library/bb928212.aspx

    Scribe

    www.scribesoft.com
    Best Regards, Donna
    Monday, February 9, 2009 3:59 PM