Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom module transferring data #32

Closed
csdougliss opened this issue Dec 23, 2015 · 8 comments
Closed

Custom module transferring data #32

csdougliss opened this issue Dec 23, 2015 · 8 comments

Comments

@csdougliss
Copy link

How do I get the tool to simply copy the data from custom modules (such as tables) to the new M2 database?

If I recreate the module that is fine, but then I get an error such as:

[2015-12-14 14:07:25][ERROR]: Destination documents are missing or not mapped: mst_core_urlrewrite,mst_misspell_index,mst_misspell_suggest,mst_search_index,mst_search_stopword,mst_search_synonym

How do I go about transferring this? I have installed the M2 version of the module

@ilol
Copy link

ilol commented Jan 6, 2016

@craigcarnell You should describe you custom data structure in config file.

@csdougliss
Copy link
Author

@ilol I appreciate that, but how? :)

@csdougliss
Copy link
Author

@ilol The documentation tells you how to ignore something, but not to simply copy the data across as the 2 modules exist in M1 and M2

@quangdog
Copy link

quangdog commented Jan 7, 2016

How about just manually copying the tables using sql statements yourself? Then telling the migrator to ignore the tables in the source database....

@csdougliss
Copy link
Author

@quangdog That kind of defeats the purpose of the data migration tool if it doesn't have that ability. Also you would also need to do this when doing an update.

@quangdog
Copy link

quangdog commented Jan 8, 2016

I believe that the migrator's approach is that if a table exists in M1 and M2, and the structure is the same, then the records from M1 will just copy straight to M2 without needing to specify any mapping.

So, rather than copy the entire table + data from M1 to M2 manually, just create the structure for the table in M2, and don't specifically map the table at all in the migrator. The data should move with the migration, and should be kept up to date with incrementals.

But what the heck do I know - I'm still trying to get my M1 to migrate to M2 without losing random bits of customer data along the way. ;-(

@victor-v-rad
Copy link
Collaborator

I believe that the migrator's approach is that if a table exists in M1 and M2, and the structure is the same, then the records from M1 will just copy straight to M2 without needing to specify any mapping.

Absolutely right

@ilol
Copy link

ilol commented Feb 2, 2016

@craigcarnell if you got an answer, please close the issue. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants