Ecstore1.2 data migration solution to ecstore2.3

It mainly involves data migration of products, members, and orders, especially the data migration of members.

Preliminary work:

1. Install standard ecstore2.3 (after secondary development, you need to compare whether it affects data migration)

 

Data Migration Solution

I. Members

1. Split member verification into two tables. The super administrator at the backend is a common member at the front-end.

2. Use account_type to differentiate member and administrator data and obtain 1.2 of member usernames and logon passwords.

3. Members: Basic Information migration (pay attention to the mandatory requirements for field types of the latest MySQL version. For more information, see the script APP/B2C/testcase/member_update.php)

4. the encryption algorithm for member login is the same (the login logic of 1.2 is different from that of 2.3, and you need to determine whether to make proper adjustments)

5. Increase in login mode 2.3: email address, mobile phone number, and 1.2 only user name. Therefore, set the login_type field in the sdb_pam_members table of 2.3 to: user name.

6. the email phone number in version 1.2 B2C _members is invalid. In Version 2.3, use the email phone number in pam_members to log on.

7. password_account in Version 2.3 comes from login_password in pam_account in version 1.2. The registration time is login_password.

9. The activation function is added to the mobile phone/email address of Version 2.3. You can log in to cancel the activation function and release the mobile phone number and email address;

10. Run the test script

11. Split the mailbox mobile phone field of version 1.2 into different tables of Version 2.3.

 

Product:

1. The default item field is added to the item.

2. The product comment table is changed. sdb_ B2C _member_comments (2.3 adds product_id and uses the default product_id corresponding to goods_id)

 

Supplement the order

Ecstore1.2 data migration solution to ecstore2.3