Memory Error with D7 Migration

I found that the pm_message_old table did not have an index on `mid` and that was slowing down the migrations as well. I wasn't sure the best way to add that to code because it is simply imported/old data and not part of the schema. Adding the primary key to my own table manually drastically cut down on migration time and may help others as well.

Hi @joshua-jake!

What version of D7 privatemsg do you use? I have 90% ready of migration from 7.x-1.4 version. You can test it soon, if you want.

@ivnish,

Currently running 7.x-1.4 and prepping for a migration. I did not realize you were working on adding a migration process for privatemsg. I would be happy to test it.

try it now :)

1) Use dev-version of privatemsg

2) Migration from Drupal 7 (7.x-1.4) to 2.x howto 📌 Migration or upgrade path Active

Sorry for the delay on testing. I was able to fully test the D7 migration in dev and it seems to work quite well. Only a few minor tweaks needed made to the yml files for mine to succeed. I'm not certain if these are universal changes or just for my specific migration. The required dependencies on my setup are all prefaced with upgrade_

For example my privatemsg_thread.yml migration_dependecies section looks like this:

required:
    - upgrade_d7_user
    - upgrade_d7_privatemsg_email_notify
    - upgrade_d7_privatemsg_message

So I changed all the ids and of the migration files themselves and the reference dependencies and it worked without needing any other changes. It was quite a large and varied set of data that I had to migrate as well, so well done and thank you.

Automatically closed - issue fixed for 2 weeks with no activity.

ivnish → closed merge request !12