Custom module transferring data about data-migration-tool

[ilol]

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

[craigcarnell]

@ilol I appreciate that, but how? :)

[craigcarnell]

@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]

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

[craigcarnell]

@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]

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]

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]

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