I am trying to put down some of the steps that we need to follow in any data migration projects. I have consolidated these steps after working on few migration projects and going through the some articles and documents that we used during our migration project cycle.
As per the various researchers data 65% to 70 % migration projects are failures . These failures mainly occur due some very small information gap which later becomes the major issue.So lets us try to discuss the step …

Kirill Izotov ,Managing Director, IT has provided comments on Mandeep's article , I thought of publishing it as a separate post. Please find Kirill's original comment below. This is an interesting discussion, and I would like to offer some additions to the recommendations kindly published by Mandeep Grewal.

The batch size should be considered very carefully depending on the status of the system – if the system that EIM is running on is "hot" or "cold", i.e. if users and other processes are actively performing insert/update/delete operations ("hot") or the system …

We should always follow few general guidelines for improving the EIM process and make a optimized EIM process for any EIM task.  Below are the few.

Limit tables and columns to be processed using ONLY BASE TABLES/COLUMNS configuration parameters to minimize EIM processing

Many get confused with data loading for the new siebel application starting from scratch. Below is the order in which we need to load data for new Siebel application. we should start loading data in follwing sequence to avoid problems

S_PARTY model is the major change seen in Siebel 7.X and later version. The S_PARTY table is the base table for all the party related entities: Person (Contact), User, Employee, Partner User, Account, Division, Organization, Partner Organization,