JSON-D8 Migration: By Using Available and Custom Process Plugins

In our XML to Drupal 8 bog post series, we have seen that how can we do the XML to D8 migration by just using YML file, extend the capabilities of the migration by using available Process plugins and finally extended the capabilities of the migration by using Custom Process plugins.

As the JSON to Drupal 8 migration is quite similar to XML migration so we will do the complete JSON to Drupal 8 migration in this Blog post.

As we are migrating from JSON so we have created a sample JSON file which looks like below,


Our migration configuration entity (YML) file under config/install defines Source (JSON file and fields in it), Destination (Drupal entity) and Field mappings (Process plugins). It looks like below,



The only change between XML and JSON migration is "data_parser_plugin" as shown below,

 
Data parser plugin is part of Migrate Plus module. It means we don't need to write custom code for most of the cases while migrating from XML or JSON to Drupal 8. The interesting part is that XML and JSON migrations are quite similar. All the available / custom process plugins will be used in same way. Even the source fields are defined in same way. If you compare the migrate_xml_d8_custom and migrate_json_d8_custom custom modules, you will notice that there is just one line change in migration configuration entity (migrate_plus.migration.pages_content.yml)!

Next we have created the custom process plugin in src/Plugin/migrate/process/ContentTypePlugin.php. This custom process plugin uses 'site_url' JSON field to determine the content type (article or basic page) based on the requirements. Custom process plugin needs to be placed under /src/Plugin/migrate/process/ as per the Drupal PSR-4 standards. The plugins in Drupal 8 uses Annotations to define the name of the plugin. Our custom plugin looks like below,


Finally migration has been executed in same way as in XML to D8 migration using "drush mi pages_content" command and we got all the data on D8 site in different content types as expected. It looks like below,

https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjItMzc5StbeVj9dHMuH9pwgdjP_PfwbN4cO-qT8ibcxlSUGmAd6CEYAGO0e_4LfaRPT9JUEL189m8i-fvjvkwnDlus_Qul1pFr7KgtBIygCPCTEJeGryq_ktjhlbo1IdU27U0/s640/d8_content_page_article.png

The source code is also available on Git repository.

We can write more custom process plugins based on our requirements and use them to do custom migrations!

Comments

yeardlivaden said…
Aesthetic Solutions For New Earrings | TITanium Arts
For more information mens black titanium wedding bands on the new earrings, visit TITanium Arts.com. All products ford fiesta titanium are tested and shipped to titanium nipple bars you with no titanium nitride questions titanium quartz asked!
9:57 PM
Post a Comment

Popular posts from this blog

Simple Meditation

Set small goals, such as meditating for two minutes every morning. When that feels OK, up the time to 5, 10 or 20 minutes. 1) Find a comfortable seat - where you can sit up tall, either crosslegged on the floor or in a chair. Close your eyes or soften the gaze so you are not focusing on anything in particular. Place the hands with the palms down on the tops of the thighs. 2) Take a moment to notice the sensation of sitting - become aware of the ground or chair beneath you, and the parts of your body in contact with them. Now bring your focus to your hands, noticing the weight of them on the thighs, and the feel of the fabric of your clothes.  3) Now begin to notice how your breath feels in your body as you inhale and exhale. Make no effort to change the breath, simply let your natural breath flow in and out. 4) Aim to stay focussed on these sensations of the breath, but when you notice the mind wandering, acknowledge the thought, then come back to the breath again.  5) When yo...
Read more

Custom MySQL Database to Drupal 8 Migration

Image
There are thousands of websites which are using MySQL as database. If we need to migrate data from Websites, which are using MySQL database, to Drupal 8 then we can use this blog post as starting point. We have a sample MySQL Database 'mysql_custom_db' which contains two tables, users and pages. The data in 'users' table looks like below,   The data in 'pages' table looks like below, As all the fields in 'users' table, from source database, will map to User entity in Drupal 8 site so we don't need make any changes there. But as we are migrating 'pages' table data to 'Basic Page' content type in Drupal 8 site, so we need to create required fields in 'Basic Page' content type. We have created the fields in 'Basic Page' content type and it looks like below, In our migration, field mapping between source site (pages) and destination site (Basic Page' content type) is like below, city...
Read more