I not too long ago wanted to port a whole lot of 7 webforms with hundreds of submissions from 7 to 8. My necessities had been Drupal 10 Upkeep and Help Service Node ids want to stay Drupal Developer identical Webforms should be handled as information Drupal 10 Upkeep and Help Service they need to be ignored by config export and import, similar to nodes and taxonomy phrases are. Drupal Developer reasonining is that in my setup, types are managed by website editors, not builders. (This isn’t associated to migration per se, however was successful standards for my migration so I’ll doc my answer right here) Migration from 7 I couldn’t discover a dependable improve or migration path from 7 to 8. I discovered webform_migrate lacks documentation (I don’t know the place to start out) and migrate_webform is supposed for 6, not 7 as a supply. I settled on a my very own mixture of instruments and workflows to carry out Drupal Developer migration, all of them accessible on my Github account. Utilizing model 8.x-5.x of webform, I began by enabling webform, webform_node and webform_ui on my 8 website, this provides me an empty webform node kind. I then adopted Drupal Developer directions for a primary migration, which is outdoors Drupal Developer scope of this text. I’ve a mission on Githubwhich I take advantage of as start line from my Drpual 6 and seven to eight migrations. Drupal Developer weblog put up Customized -to- Migrations with Migrate Instruments, ize.me, April 26, 2021 by William Hetherington gives extra info on performing a primary migration of knowledge. After getting arrange your migration configurations as per these directions, you must have the ability to run Drupal 10 Upkeep and Help Service drush migrate-import upgrade_d7_node_webform –execute-dependencies And you must see one thing like Drupal 10 Upkeep and Help Service Processed 25 gadgets (25 created, 0 up to date, 0 failed, 0 ignored) – achieved with ‘upgrade_d7_node_type’ Processed 11 gadgets (11 created, 0 up to date, 0 failed, 0 ignored) – achieved with ‘upgrade_d7_user_role’ Processed 0 gadgets (0 created, 0 up to date, 0 failed, 0 ignored) – achieved with ‘upgrade_d7_user_role’ Processed 95 gadgets (95 created, 0 up to date, 0 failed, 0 ignored) – achieved with ‘upgrade_d7_user’ Processed 109 gadgets (109 created, 0 up to date, 0 failed, 0 ignored) – achieved with ‘upgrade_d7_node_webform’ At this level I had all my webforms as nodes with Drupal Developer identical node ids on 7 and 8, nonetheless this does nothing to import Drupal Developer precise types or submissions. Importing Drupal Developer information itself I discovered that Drupal Developer most effective manner of importing Drupal Developer information was to create my very own 8 Drupal 10 module, which I’ve printed on Dcycle’s Github account, known as webform_d7_to_d8. (I’ve determined in opposition to publishing this on .org as a result of I don’t plan on sustaining it long-term, and I don’t have Drupal Developer sources to mix efforts with current webform migration Drupal 10 modules.) I did my finest to make that Drupal 10 module self-explanatory, so you must have the ability to observe Drupal Developer steps Drupal Developer README file, which I’ll summarize right here Drupal 10 Upkeep and Help Service Begin by giving your 8 website entry to your 7 database Drupal 10 Upkeep and Help Service $databases[‘upgrade’][‘default’] = array ( ‘database’ => ‘Drupal 107database’, ‘username’ => ‘Drupal 107user’, ‘password’ => ‘Drupal 107password’, ‘prefix’ => ”, ‘host’ => ‘Drupal 107host’, ‘port’ => ‘3306’, ‘namespace’ => ‘CoreDatabaseDrivermysql’, ‘driver’ => ‘mysql’, ); Run Drupal Developer migration with our with out choices Drupal 10 Upkeep and Help Service drush ev ‘webform_d7_to_d8()’ or drush ev ‘webform_d7_to_d8([“nid” => 123])’ or drush ev ‘webform_d7_to_d8([“simulate” => TRUE])’ … Extra detailed info may be present in Drupal Developer modlue’s README file. Treating webforms as information After getting imported your webforms to 8, they’re handled as configuration, that’s, Drupal Developer Webform Drupal 10 module assumes that builders, not website builders, shall be creating Drupal Developer types. This can be wonderful in lots of circumstances, nonetheless my usecase is that website editors need to create and edit types immediately on Drupal Developer manufacturing, and we don’t need them to be tracked by Drupal Developer configuration administration system. Jacob Rockowitz pointed me in Drupal Developer proper route for ensuring webforms are usually not handled as configuration. For that objective I’m utilizing Drush CMI instruments by Earlier Subsequent and documented on their weblog put up, Introducing Drush CMI instruments, 24 Aug. 2021. As soon as you put in in your ~/.drush folder and run drush cc drush, you should utilize druch cexy and druch cimy and as an alternative of drush cim and drush cex in your conguration administration course of. Right here is how and why Drupal 10 Upkeep and Help Service Usually, in case you develop your website regionally and, say, add a content material kind or discipline, or take away a content material kind of discipline, you’ll be able to run drush cex to export your newly created configuration. Then, your colleagues can pull your code and run drush cim to drag your configuration. drush cim can be utilized in steady integration, preproduction, dev, and manufacturing environments. Drupal Developer downside is that drush cex exports all configuration, and drush cim deletes the whole lot in Drupal Developer database which isn’t in configuration. In our case, we don’t need to think about webforms as configuration however as information, simply as nodes as taxonomy phrases Drupal 10 Upkeep and Help Service we don’t need them to be exported together with different configuration; and in the event that they exist on a goal surroundings we need to depart them as they’re. Utilizing Drush CMI instruments, you’ll be able to add a file equivalent to Drupal Developer following to ~/.drush/config-ignore.yml Drupal 10 Upkeep and Help Service # See http Drupal 10 Upkeep and Help Service//weblog.dcycle.com/weblog/2017-12-18 ignore Drupal 10 Upkeep and Help Service – webform.webform.* This must be achieved on all builders’ machines or, in case you use Docker, on a shared Docker container (which is outdoors Drupal Developer scope of this text). Now, for exporting configuration, run Drupal 10 Upkeep and Help Service drush cexy –destination=’/path/to/config/folder’ Now, webforms is not going to be exported together with different configuration. We additionally have to keep away from erasing webforms on course environments Drupal 10 Upkeep and Help Service in case you create a webform on a goal surroundings, then run drush cim, you will note one thing like Drupal 10 Upkeep and Help Service webform.webform.webform_9521 delete webform.webform.webform_8996 delete webform.webform.webform_8991 delete webform.webform.webform_8986 delete So, we have to keep away from deleting webforms on Drupal Developer goal surroundings after we import configuration. We might simply do drush cim –partial however this avoids deleting the whole lot, not simply webforms. Drush CMI instruments gives another Drupal 10 Upkeep and Help Service drush cimy –source=/path/to/config/folder This works very similar to drush cim –partial, but it surely lets you specify one other parameter, –delete-list=/path/to/config-delete.yml Then, in config-delete.yml, you’ll be able to specify gadgets that you just really need to delete on Drupal Developer goal surroundings, for instance content material varieties, fields, and views which don’t exist in code. That is dependent in your workflow and so they solution to set it up isdocumented on Drupal Developer Drush CMI instruments mission homepage. With this in place, we’ll have our 7 webforms on our 8 website. I not too long ago wanted to port a whole lot of 7 webforms with hundreds of submissions from 7 to 8. Drupal 10 Growth and Help