Magento Database Expert: Customers and Orders Migration

========= Applicants must have deep knowledge of Magento data structure. ====== I will be asking follow up questions in the interview process, so please do not apply unless you are very well versed in how Magento works and the tables involved. ==== JOB DESCRIPTION: We have two live Magento Stores, that we want to merge together. They have been operating indepedently from each other for about a year. They are both the same version of Magento, 1.6.0. We are using one of them as the main store and discontinuing the other. We have already migrated the products over to the main store. The products have the same SKU in both stores, so that is how order_item data will be mapped. We now need a collection of processes, or script, that will migrate the customers and orders and all related data to the main store from the other. We currently have a CakePHP app that has access to the databases for both stores. I could provide a Cake Development environment, if the migration script can be written as a CakePHP shell script. If you feel more comfortable using something else, I am open to discuss. I can provide a magento development environment. With some test data, if needed. This job is for a milestone: Migrate 1 customer with all related order data. This will include, but not be limited to, the following datasets: quotes/quote_grid quote_items orders/order_grid order_items invoices/invoice_grid invoice_items customers customer_addresses shipments/shipments_grid shipment_items transactions creditmemos/creditmenos_grid creditmemo_items wishlists ==================== I WANT TO MAKE THIS CLEAR: I do not want a script that simply dumps all tables from one database to the other. =================== Some of these tables are obviously related to each other, so the keys and such will need to be preserved, and/or mapped as the rows get inserted. This is the main reason that I would like to do one customer at a time. So that each dataset is done per customer. This means that all processes should be done similarly. For example, when it comes to order_items, we select all the order items for the one order, and we insert them one at a time, mapping the product_ids, and any other mapped ids over in that process. So, we have little to no need for a migration index, because each time we insert a record, we use the last insert id to migrate all the related data. This process will allow for testing of data as the migration progresses. The Magento install that we are migrating to, has a store 1 that is active. We will be creating a store 2 on the same database. So the order increment id can remain the same except for the prefix store number on that increment id will be 2 instead of one. We can discuss budget for the entire job. Please remember that this is a milestone job for Migrating 1 customer with all that customer's related order data. Thank you.