I couldn't make a patch for the module as it requires more changes than I thought initially and also I'm not using settings.php but a custom implementation. But I can share my class which might be useful to others and maybe anyone can integrate it into the module:

... the hiNode class is just an abstract class I extended from DrupalNode7Migration (part of migrate_d2d). As you can see, I do not have any fields besides the basics, in fact, nothing is custom about it at all. It is just running D2D's basic node stuff.

The webform migrations are intended to run after the nodes are in place. What I mean by that is, run your migration, then go to the "Webform Migrations" and run those in order.

I'm finding that the dev branch actually works out of the box for adding the settings, email addresses, and form components. The submissions also come through but I get an error part way through the "submitted data" migration.

My guess is that to get this thing to work for D7->D7 we will need to:

1. add a select option to the configure form, and
2. update the query for the submitted_data migration.

berdyshevCreditAttribution: berdyshev at AMgrade commented 13 November 2017 at 12:32

patched applied without any issues and works well at the moment.

@ckng, One thing. I've faced an issue with configuration page. For example, I've unchecked "Create a node migration by default" in order to specify my custom migration of nodes. But when I specified PHP Class name in the following field, I got the error "Error: Call to a member function getGroup() on null in migrate_migrations()". After debugging I've found that the migration name should be filled in this field. Can we change the wording?