<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Complex CMS Migration Service - Migrate Content (Posts about blog)</title><link>https://migratecontent.com/</link><description></description><atom:link href="https://migratecontent.com/categories/blog.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 22 Mar 2026 16:22:29 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Fixing Access Forbidden (403) issues after migrating WordPress to a static site</title><link>https://migratecontent.com/fixing-access-forbidden-403-issues-after-migrating-wordpress-to-a-static-site/</link><dc:creator>Anthony Lopez-Vito</dc:creator><description>&lt;p&gt;After migrating a WordPress site to static files, Google Search Console may start sending you notifications about page indexing problems. Often the issue will be marked as '&lt;em&gt;Blocked due to access forbidden (403)&lt;/em&gt;', a fairly common error that can have different causes, depending on how your website and server is set up.&lt;/p&gt;


&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/no-entry-Lucian-Alexe-Unsplash-l0w1ftNPZ9s.jpg" alt="No entry road stock photo - Access Forbidden 403 error" class="figure-img img-fluid rounded" width="800" height="417"&gt;
&lt;/figure&gt;

&lt;p&gt;This article specifically deals with the case when:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;You previously had a working WordPress installation;&lt;/li&gt;
&lt;li&gt;You migrate the site to static HTML files on an Apache web server;&lt;/li&gt;
&lt;li&gt;Google Search Console starts complaining about page indexing problems.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If this does not apply to your situation, the proposed solution may not work but you will still find the explanation useful in diagnosing the problem.&lt;/p&gt;
&lt;h2&gt;Table of contents&lt;/h2&gt;
&lt;div class="toc"&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href="https://migratecontent.com/fixing-access-forbidden-403-issues-after-migrating-wordpress-to-a-static-site/#forbidden-403"&gt;The Forbidden 403 error&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://migratecontent.com/fixing-access-forbidden-403-issues-after-migrating-wordpress-to-a-static-site/#wordpress-requests"&gt;How WordPress serves your browser requests&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://migratecontent.com/fixing-access-forbidden-403-issues-after-migrating-wordpress-to-a-static-site/#static-files"&gt;Serving static files&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://migratecontent.com/fixing-access-forbidden-403-issues-after-migrating-wordpress-to-a-static-site/#directory-index"&gt;Web server directory index&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://migratecontent.com/fixing-access-forbidden-403-issues-after-migrating-wordpress-to-a-static-site/#generating-static-site"&gt;Generating static HTML files from a WordPress site&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://migratecontent.com/fixing-access-forbidden-403-issues-after-migrating-wordpress-to-a-static-site/#why-forbidden"&gt;Why access is forbidden&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://migratecontent.com/fixing-access-forbidden-403-issues-after-migrating-wordpress-to-a-static-site/#how-to-fix"&gt;How to fix the Access Forbidden (403) error&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;

&lt;h2 id="forbidden-403"&gt;The Forbidden 403 error&lt;/h2&gt;
&lt;p&gt;Being in the 4XX category of HTTP response codes, &lt;em&gt;Access Forbidden (403)&lt;/em&gt; is a client-side error that may show in a message similar to the following combinations:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;Access Forbidden (403)&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;403 Forbidden&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;HTTP 403&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;HTTP Error 403 – Forbidden&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Forbidden: You don't have permission to access [directory path] on this server&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The Google Search Console notification email will be about page indexing problems with  '&lt;em&gt;Blocked due to access forbidden (403)&lt;/em&gt;' as one of the Top Issues.&lt;/p&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/anothercoffee-google-search-console-page-indexing-issues.png" alt="Google Search Console Page indexing issues" class="figure-img img-fluid rounded" width="498" height="348"&gt;
    &lt;figcaption&gt;A typical Access Forbidden (403) notification from the Google Search Console&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;Nevertheless, it being a client-side error doesn't necessary isolate the problem to your browser. Many solutions online will advise you to clear your cache or refresh the page. This is easy to do and usually a sensible first step but if you found the issue via a Google Search Console notification after a WordPress migration, these recommendations won't help.&lt;/p&gt;
&lt;p&gt;The 403 response code essentially means that a web client, such as your browser, does not have permission to access the requested resource. The web server understands the request but can't allow access due to file permissions settings or a server misconfiguration. When it comes to WordPress, the error will almost certainly be due to a misbehaving plugin, a &lt;a href="https://kinsta.com/blog/403-forbidden-error/" target="_blank" rel="noreferrer noopener nofollow"&gt;corrupt .htaccess file or incorrect file permissions&lt;/a&gt;. However, if you've recently converted your WordPress installation to a static site, the error will most likely have a different cause.&lt;/p&gt;
&lt;p&gt;To understand why the &lt;em&gt;Access Forbidden&lt;/em&gt; error happens, it's worth reviewing the differences between how the WordPress content management system (CMS) serves content and how a static site responds to web client requests.&lt;/p&gt;

&lt;h2 id="wordpress-requests"&gt;How WordPress serves your browser requests&lt;/h2&gt;
&lt;p&gt;WordPress is a database-driven Content management system (CMS). Most of the content is stored in a database and URLs generally do not correspond to any files in the web server's filesystem. Instead, URLs are external references to the database content. WordPress calls these references &lt;em&gt;permalinks&lt;/em&gt; and its rewriting engine uses internal &lt;a href="https://codex.wordpress.org/Using_Permalinks"&gt;rules&lt;/a&gt;, specified in the &lt;a href="https://codex.wordpress.org/Using_Permalinks#Choosing_your_permalink_structure"&gt;permalink settings&lt;/a&gt;, to build permalinks dynamically. When a client requests a page from the site, WordPress takes care of serving the correct content. Included with the pages will be any XML-based RSS (Really Simple Syndication) feeds. WordPress will send the HTML page or an XML feed, depending on what the client requests.&lt;/p&gt;
&lt;p&gt;For example, if you set the permalink settings to the &lt;em&gt;Post name&lt;/em&gt; structure, WordPress will generate a HTML post when you browse to the following URL:&lt;br&gt;&lt;code&gt;https://example.com/your-post/&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;The RSS feed for that post will be at:&lt;br&gt;&lt;code&gt;https://example.com/your-post/feed/&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;RSS feeds are normally parsed by an RSS client rather than for displaying directly in the browser window so requesting the RSS feed resource will not send HTML. Instead WordPress will generate XML for the feed.&lt;/p&gt;

&lt;h2 id="static-files"&gt;Serving static files&lt;/h2&gt;
&lt;p&gt;By definition, static sites have no way of dynamically generating content based on the browser request. You make a request to the web server at a given URL and if the resource is present with the correct access permissions, the web server will go ahead and serve the file. The URL for a static site will normally look something like:&lt;br&gt;&lt;code&gt;https://example.com/your-post.html&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;If you have an RSS feed, it might look something like:&lt;br&gt;&lt;code&gt;https://example.com/feed.xml&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Notice that the request includes the path to the file, such as &lt;code&gt;your-post.html&lt;/code&gt; or &lt;code&gt;feed.xml&lt;/code&gt;. The file is not present in a WordPress permalink because, as mentioned previously, it is only a reference to the actual content stored in the database.&lt;/p&gt;

&lt;h2 id="directory-index"&gt;Web server directory index&lt;/h2&gt;
&lt;p&gt;Web servers such as Apache also have a &lt;a href="https://httpd.apache.org/docs/2.4/mod/mod_dir.html#directoryindex" target="_blank" rel="noreferrer noopener nofollow"&gt;Directory Index directive&lt;/a&gt;. This is a configuration that can set the server to automatically send a file when a client makes a request without a filename in the URL. The file known as the directory index and is normally named &lt;code&gt;index.html&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Web servers such as Apache also have a &lt;a href="https://httpd.apache.org/docs/2.4/mod/mod_dir.html#directoryindex" target="_blank" rel="noreferrer noopener nofollow"&gt;Directory Index directive&lt;/a&gt;. In the early days of the web, you could browse to a folder in the web server filesystem and get a listing of all the files present. For security, most web hosts now disable this feature for most of their hosting services. The Directory Index directive is a configuration that can set the server to automatically send a file when a client request only includes the folder name in the URL. For most hosting services, the standard directory index files are normally &lt;code&gt;index.html&lt;/code&gt; and &lt;code&gt;index.php&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Say a client makes a request for the following:&lt;br&gt;&lt;code&gt;https://example.com/docs/&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;If the directory index is set to &lt;code&gt;index.html&lt;/code&gt;, the server would return:&lt;br&gt;&lt;code&gt;http://example.com/docs/index.html&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The &lt;code&gt;index.html&lt;/code&gt; renders as a web page in the browser. Directory index resources can also be set to other file types like &lt;code&gt;index.txt&lt;/code&gt; or &lt;code&gt;index.xml&lt;/code&gt;.&lt;/p&gt;

&lt;h2 id="generating-static-site"&gt;Generating static HTML files from a WordPress site&lt;/h2&gt;
&lt;p&gt;WordPress plugins such as &lt;a href="https://wordpress.org/plugins/simply-static/" target="_blank" rel="noreferrer noopener nofollow"&gt;Simply Static&lt;/a&gt; will crawl your site to generate static HTML file copies for the pages. Since WordPress includes RSS feeds, static XML copies will also be generated for these feeds. The tables below show typical WordPress permalinks and their equivalents after static HTML copies are generated.&lt;/p&gt;
&lt;figure class="wp-block-table"&gt;
&lt;table class="has-fixed-layout"&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th style="width:30%"&gt;Page type&lt;/th&gt;
&lt;th&gt;WordPress permalink&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Page content&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;code&gt;https://example.com/your-post/&lt;/code&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RSS feed&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;code&gt;https://example.com/your-post/feed/&lt;/code&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;/figure&gt;
&lt;figure class="wp-block-table"&gt;
&lt;table class="has-fixed-layout"&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th style="width:30%"&gt;Page type&lt;/th&gt;
&lt;th&gt;Static file URL&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Page content&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;code&gt;https://example.com/your-post/index.html&lt;/code&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RSS feed&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;code&gt;https://example.com/your-post/feed/index.xml&lt;/code&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;/figure&gt;
&lt;p&gt;Once again notice that the static site specifies the filename in the path whereas the WordPress permalink, when set to the &lt;em&gt;Post name&lt;/em&gt; structure, does not.&lt;/p&gt;
&lt;h2 id="why-forbidden"&gt;Why access is forbidden&lt;/h2&gt;
&lt;p&gt;We have all the puzzle pieces to understand why you would get the &lt;em&gt;Access Forbidden (403)&lt;/em&gt; error and how you can fix the problem. After you migrate your WordPress site to static files, the old permalink paths to pages will still serve a web page because most hosting providers have &lt;code&gt;index.html&lt;/code&gt; as a directory index resource.&lt;/p&gt;
&lt;p&gt;You can request the URL in the WordPress post name permalink format:&lt;br&gt;&lt;code&gt;https://example.com/your-post/&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;The static file generator would have created an index.html in this location:&lt;br&gt;&lt;code&gt;https://example.com/your-post/&lt;/code&gt;index.html&lt;/p&gt;
&lt;p&gt;The webserver sees the &lt;code&gt;index.html&lt;/code&gt; in the filesystem and delivers it to the browser which can render the web page content. Human site visitors will be perfectly happy because they receive the web page resources they expect. However, Googlebot, Google's web page crawler, will spider through your site &lt;em&gt;including the RSS feed locations&lt;/em&gt;. Remember, the RSS feed folders will contain an &lt;code&gt;index.xml&lt;/code&gt;. XML files are not normally a default directory index resource for most web hosts. Since there is no &lt;code&gt;index.html&lt;/code&gt; file in the feed folder, the web server thinks it's being asked to deliver a file listing. Again remember that file listings are disabled by most web hosts for security. Thus you get the error:&lt;/p&gt;
&lt;p class="has-text-align-center"&gt;&lt;code&gt;Access Forbidden (403)&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;You are forbidden by the web server to access that folder listing.&lt;/p&gt;

&lt;h2 id="how-to-fix"&gt;How to fix the Access Forbidden (403) error&lt;/h2&gt;
&lt;p&gt;Now that we know exactly why we get this error we attempt a fix. If your host runs Apache, the solution will likely be simple. Edit or create the &lt;code&gt;.htaccess&lt;/code&gt; file in the root of your site and add &lt;code&gt;index.xml&lt;/code&gt; to the list of directory index resources. For example, if it not already there, add the following line somewhere near the top of the file:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;DirectoryIndex index.html index.php index.xml&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;The &lt;code&gt;index.xml&lt;/code&gt; in the list will tell Apache to serve the XML file when Googlebot requests the RSS feed directory. While you're doing this, inspect a few o the feed directories to make sure the &lt;code&gt;index.xml&lt;/code&gt; files have the correct permissions (usually &lt;code&gt;775&lt;/code&gt; for most server setups) and the correct ownership. The ownership settings should be:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;user&lt;/code&gt;&lt;/strong&gt; is the user account with root privileges on your web server.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;group&lt;/code&gt;&lt;/strong&gt; is usually &lt;strong&gt;&lt;code&gt;www-data&lt;/code&gt;&lt;/strong&gt; or &lt;strong&gt;&lt;code&gt;apache&lt;/code&gt;&lt;/strong&gt; but you may need to check this with your hosting provider.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can test your changes by pointing your browser to a few feed directories to see if the server returns XML. Remember to leave out the &lt;code&gt;index.xml&lt;/code&gt; file and specify the directory only. For example:&lt;br&gt;&lt;code&gt;https://example.com/your-post/feed/&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;If your browser displays the RSS feed XML, you know the problem has been solved and can be reasonably confident that Googlebot won't encounter the 403 error.&lt;/p&gt;
&lt;p&gt;This may not work if you're running a VPS server for your site where some more in-depth configuration may be needed, such as editing your Apache configuration files. Also, &lt;code&gt;.htaccess&lt;/code&gt; is not used by other web servers such as NGINX. In these cases, your next port of call should be to contact your hosting provider. Tell them that you would like to add &lt;code&gt;index.xml&lt;/code&gt; to the directory index resources so that the XML file is served when a visitor lands in a directory. Most good hosting companies will be able to guide you on your options or make the change on your behalf. After you've applied the fix, be sure to go to your Google Search Console to revalidate the affected page.&lt;/p&gt;

&lt;div class="footnotes"&gt;
    &lt;p&gt;Photo by &lt;a href="https://unsplash.com/@lucian_alexe?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText" target="_blank" rel="nofollow"&gt;Lucian Alexe&lt;/a&gt; on &lt;a href="https://unsplash.com/photos/l0w1ftNPZ9s?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText" target="_blank" rel="nofollow"&gt;Unsplash&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;</description><category>apache</category><category>blog</category><category>help</category><category>migration</category><category>seo</category><category>sys admin</category><category>troubleshooting</category><category>wordpress</category><guid>https://migratecontent.com/fixing-access-forbidden-403-issues-after-migrating-wordpress-to-a-static-site/</guid><pubDate>Thu, 09 Feb 2023 01:15:57 GMT</pubDate></item><item><title>A guide to WordPress Backups and Staging</title><link>https://migratecontent.com/wordpress-backups-and-staging-guide/</link><dc:creator>Anthony Lopez-Vito</dc:creator><description>&lt;div style="margin: 2em 0 2em 0; padding: 1em 2em 1em 2em; font-weight: 400; text-align: center; color: #444; background-color: #f5f5f5; border: 3px solid #e9ecef;"&gt;&lt;em&gt;This &lt;strong&gt;WordPress Backups and Staging Guide&lt;/strong&gt; is a guest post by &lt;a href="https://blogvault.net/author/melinda/" rel="author"&gt;Melinda Bartley&lt;/a&gt;.&lt;/em&gt;&lt;/div&gt;

&lt;p&gt;If you've run a WordPress site long enough, you'd know how making changes to it can be tricky. Sometimes, even minor changes can cause major glitches. This makes backups and staging such lifesavers!&lt;/p&gt;
&lt;p&gt;Every WordPress site should have backup and staging solutions in place. And not just any solution, one that actually works! I say this because in my experience, relying on host backups and staging environments have too many limitations and a tedious process. So I turned to plugins, but there too, I found so many options, it was hard to pick the right one.&lt;/p&gt;
&lt;p&gt;In my quest to get a permanent solution, I stumbled upon BlogVault. It was easy-to-use and reliable with a great support team behind it. Ever since, it has been my go-to for WordPress backups and staging.&lt;/p&gt;
&lt;p&gt;So today, I'm sharing everything what I think WordPress site owners should know about backups and staging and why BlogVault works best.&lt;/p&gt;
&lt;p&gt;Let's begin with a few basics.&lt;/p&gt;
&lt;h2&gt;Difference Between Backup and Staging&lt;/h2&gt;
&lt;p&gt;Many ask If I have a backup, why do I need staging? Well, the two solve very different problems. Backups are for reverting to a previous version when a problem arises on the site.&lt;/p&gt;
&lt;p&gt;For example, you run an update on your website and it causes your site to malfunction. You find that plugins are not compatible with the new version of WordPress. It would take considerable time to update these plugins or find replacements. To solve the issue immediately and get your site back to normal, you can restore your backup.&lt;/p&gt;
&lt;p&gt;Backups come in handy when things go wrong such as botched updates, human errors, presence of malware, and so on.&lt;/p&gt;
&lt;p&gt;Coming to staging, it enables you to create a clone of your WordPress website. This is done specifically for development. You can try out new themes, plugins, designs and layouts. You can test out updates and even test restore your backup! None of the changes you make will affect your live site.&lt;/p&gt;
&lt;p&gt;There are staging solutions that have a feature to merge your changes. This is extremely handy because you might make multiple changes and it would take time to replicate the same on your live site. So you can just push the changes to your live site. Simply put, staging enables progress!&lt;/p&gt;
&lt;p&gt;Now that you know why you need both solutions, let's check out the backup solutions available for WordPress sites.&lt;/p&gt;
&lt;h2&gt;WordPress Backup Solutions&lt;/h2&gt;
&lt;p&gt;There are many options to backup your WordPress site, but not all of them are easy to use or reliable. The main options available to back up your site are – manually, using a plugin, or through your web host.&lt;/p&gt;
&lt;h3&gt;Manual Backups&lt;/h3&gt;
&lt;p&gt;For this, you need to access your web hosting account. Once you've logged in, go to&lt;em&gt; cPanel &amp;gt; File Manager &amp;gt; Public_Html&lt;/em&gt;. Here, you'll see all your WordPress files. Simply compress and download them.&lt;/p&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/Hosting-Control-Panel-Manual-Backups.png" class="figure-img img-fluid rounded" alt="Hosting Control Panel Manual Backups" width="653" height="408"&gt;
    &lt;figcaption class="figure-caption text-center"&gt;(Image source: &lt;a href="https://wpengine.com/"&gt;WP Engine&lt;/a&gt;)&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;It seems simple enough. But there are issues with this method. For one, the process is time-consuming. Spending time taking manual backups regularly is simply not feasible when you have tons of other things to focus on. Plus, you need to take responsibility to encrypt your data and store the backup locally. A backup has all the information on your website and needs to be stored securely. If hackers get their hands on an unencrypted backup, it's already a data breach, but you can be sure your site will be hacked as well.&lt;/p&gt;
&lt;p&gt;But above all, the biggest hassle with this method is the restoration process. Sometimes, the backup just doesn't work at all. Other times, you restore your site only to find it malfunctioning or missing functionalities. Which means more time wasted on troubleshooting and debugging troubles. This is why I prefer using a plugin. But among these too, there are so many options available, how do you choose one?&lt;/p&gt;
&lt;p&gt;Well, after trying out a couple of them, I stuck with BlogVault. It's great for backups and even offers inbuilt staging at no additional cost.&lt;/p&gt;
&lt;h3&gt;Backups with a WordPress Plugin – &lt;a href="https://blogvault.net/"&gt;BlogVault&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;To start off, setting up BlogVault was easy to use – with a simple install and activate process. Once you sign up, the backup automatically runs. It gives you the following options which I think is not only cool but essential for WordPress:&lt;/p&gt;
&lt;ul&gt;
&lt;li style="list-style-type: none;"&gt;
&lt;ul&gt;
&lt;li&gt;The option to schedule your backups. Plus, you can take a backup on demand whenever you want, any number of times. This is good to have when you want to make major changes to your site or roll out big updates. Taking a backup before any major change is absolutely necessary.&lt;/li&gt;
&lt;li&gt;It's all automated so you don't have to worry about the technicalities.&lt;/li&gt;
&lt;li&gt;The restore process is just a few clicks. It takes a few minutes and it's guaranteed to work. So you needn't worry about your site breaking or losing data.&lt;/li&gt;
&lt;li&gt;The process is handled offsite on their own servers so it doesn't affect the performance or speed of your site. Plus, it doesn't take a full backup every single time. It smartly copies one full backup and then subsequently, only the changes made each time are backed up.&lt;/li&gt;
&lt;li&gt;Lastly, your backup is encrypted and multiple copies of it are stored securely. That takes away the pain of storage.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/BlogVault-WordPress-Backup-Plugin.png" class="figure-img img-fluid rounded" alt="Creating a backup using the BlogVault WordPress Backup Plugin" width="818" height="378"&gt;
&lt;/figure&gt;

&lt;p&gt;Apart from this, there are handy features like 365-day archives, real-time backups, website management, &lt;a href="https://migratecontent.com/drupal-to-wordpress-migration-service/"&gt;site migrations&lt;/a&gt;, multiple site management, uptime monitoring, and staging.&lt;/p&gt;
&lt;p&gt;Next, you can also back up your website using your web host itself. I've checked out two of the most popular ones.&lt;/p&gt;
&lt;h3&gt;Backups with your Host – &lt;a href="https://wpengine.com/"&gt;WP Engine&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;WP Engine takes backups for all environments by default. This includes production staging, development, and legacy staging. It's automated, encrypted, and stored offsite on Amazon S3. You can also take manual backups. It keeps up to 40 backup points. Older data up to 60 points may be accessible but you need to contact their support team for that.&lt;/p&gt;
&lt;p&gt;To access a backup, log into your user portal. Go to &lt;em&gt;sites &amp;gt; environment name &amp;gt; backup points&lt;/em&gt;. You'll find your backups here. You can also create a backup on demand.&lt;/p&gt;
&lt;p&gt;To restore, simply click on the backup point you want and click the Restore button.&lt;/p&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/WP-Engine-Backups.png" class="figure-img img-fluid rounded" alt="Creating backups in WP Engine" width="768"&gt;
    &lt;figcaption class="figure-caption text-center"&gt;(Image source: &lt;a href="https://wpengine.com/"&gt;WP Engine&lt;/a&gt;)&lt;/figcaption&gt;
&lt;/figure&gt;


&lt;p&gt;The process seems simple enough. But WP Engine also has some drawbacks. The restore process can take several minutes to several hours. And it's important to note that they do not copy all files of your site. The following files aren't included:&lt;/p&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/WP-Engine-Backups-Excluded-Files.png" class="figure-img img-fluid rounded" alt="Files excluded with WP Engine backups" width="505" height="384"&gt;
&lt;/figure&gt;

&lt;p&gt;Additionally, it's a destructive backup which means, during the restoration process, all content is overwritten. So, if you have files on your website that are not present in your backup, they will be wiped out. Your site will be restored to the contents of the backup alone.&lt;/p&gt;

&lt;h3&gt;Backups with your Host – &lt;a href="https://kinsta.com/"&gt;Kinsta&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Kinsta provides daily automatic backups for your WordPress site. It also has system-generated backups for all the sites listed in your account. The backup is a snapshot of your website's files, database, redirects, and Nginx configuration. When you restore your backup up, all of these elements will be rolled back to when the backup was taken.&lt;/p&gt;
&lt;p&gt;You can also create manual backups if you want one immediately and don't want to wait for the scheduled one to run. You need to visit the 'Backups' tab, click on the 'Manual' tab. Here, you'll find the 'Backup Now' button for on-demand backups.&lt;/p&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/Kinsta-Backups-1024x603.png" class="figure-img img-fluid rounded" alt="Creating backups on Kinsta" width="640" height="377"&gt;
    &lt;figcaption class="figure-caption text-center"&gt;(Image source: &lt;a href="https://kinsta.com/"&gt;Kinsta&lt;/a&gt;)&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;The duration for which your backups are stored depends on your hosting plan. It can vary between 14 days and 30 days. Kinsta also allows you to increase the frequency of your backups to hourly and 6-hour backups at a premium.&lt;/p&gt;
&lt;p&gt;When it comes to restoring your site, you can simply click on the 'Restore' button next to the backup of your choice. While the restore takes place, you cannot access your site. The process can take a few minutes to a few hours.&lt;/p&gt;
&lt;p&gt;What I liked about Kinsta is that it takes a backup of your site before restoration. So you can undo the restore and get back your site to as it was.&lt;/p&gt;
&lt;p&gt;That brings up to the end of backups. With a backup solution in place, we can move on to staging. Here, I'll touch upon – the manual method, show you how you can do this with the BlogVault plugin, and also talk about staging with your hosting provider.&lt;/p&gt;

&lt;h2&gt;WordPress Staging Solutions&lt;/h2&gt;
&lt;p&gt;Staging a site can be done manually through your hosting account. But it's riddled with problems. The process to create one is quite technical, and for a regular WordPress user, it's not a feasible option.&lt;/p&gt;
&lt;p&gt;Next, if you want to merge the changes you made, you need to download the updated files from your staging site and upload them to you live site. This is risky business as you could wipe out data and even crash your site.&lt;/p&gt;
&lt;p&gt;Fortunately, there are other options! You can create a staging site with your host or by using a plugin. Coming back to BlogVault, it also offers a staging feature that makes the job much easier.&lt;/p&gt;
&lt;h3&gt;Staging with BlogVault&lt;/h3&gt;
&lt;p&gt;If you've already installed BlogVault, staging is a free feature compatible with any web host. On the BlogVault dashboard, you'll see an option to 'Add staging site'. It takes a few minutes, and you'll be notified when it's done.&lt;/p&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/BlogVault-WordPress-Staging-Plugin.png" class="figure-img img-fluid rounded" alt="Creating a WordPress  staging site with the BlogVault Plugin
        width=" 640" height="377"&gt;
    &lt;figcaption class="figure-caption text-center"&gt;(Image source – &lt;a href="https://blogvault.net/wordpress-staging/"&gt;BlogVault&lt;/a&gt;)&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;The plugin handles migrating your site to a dev environment, so you don't have to bother about the file transfer and the database export and import. The staging site is password protected and blocked off from search engines so &lt;a href="https://migratecontent.com/preserving-seo-drupal-wordpress-migration/"&gt;migration does not affect your SEO&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;With everything taken care of, you simply need to start using your staging site. Once you're happy with the changes you've made, you can simply merge the changes to your live site. There's no need to upload files or replicate changes.&lt;/p&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/BlogVault-WordPress-merging-tool.png" class="figure-img img-fluid rounded" alt="BlogVault WordPress merge tool" width="671" height="344"&gt;
    &lt;figcaption class="figure-caption text-center"&gt;(Image source – &lt;a href="https://blogvault.net/wordpress-staging/"&gt;BlogVault&lt;/a&gt;)&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;You can also do a selective merge. BlogVault gives you a comparison of your live site and your staging site. You can then select which changes you want to merge to your live site. In the example below, I made changes to my plugins, themes, uploads, and a few other files. But I wanted only the changes made to plugins. By clicking on the '+' sign, I could see the list of plugins I added or modified. I selected the ones I wanted and merged in just two clicks.&lt;/p&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/BlogVault-WordPress-file-comparison-tool.png" class="figure-img img-fluid rounded" alt="BlogVault WordPress file comparison tool" width="926" height="396"&gt;
    &lt;figcaption class="figure-caption text-center"&gt;(Image source – &lt;a href="https://blogvault.net/wordpress-staging/"&gt;BlogVault&lt;/a&gt;)&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;The best part is that you can create as many staging sites as you want. So that's BlogVault. It's straightforward and easy to use. It won't break your site when you merge the changes so your site is in safe hands.&lt;/p&gt;
&lt;p&gt;Next, let's take a look at staging options with web hosting providers.&lt;/p&gt;
&lt;h3&gt;Staging with WP Engine&lt;/h3&gt;
&lt;p&gt;WP Engine gives you options to create three kinds of environments – production, staging, and development.&lt;/p&gt;
&lt;p&gt;To carry out the staging process, you first need to add your site to the user portal. Next, log into the user portal and access Sites &amp;gt; Name of your site &amp;gt; Add staging. Your staging site will be created using the backup point of the existing environment.&lt;/p&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/WP-Engine-WordPress-staging.png" class="figure-img img-fluid rounded" alt="WP Engine WordPress staging" width="1024" height="492"&gt;
    &lt;figcaption class="figure-caption text-center"&gt;(Image source – &lt;a href="https://blogvault.net/wordpress-staging/"&gt;BlogVault&lt;/a&gt;)&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;In case you don't see the staging option, you need to &lt;a href="https://wpengine.com/support/convert-single-environment-sites/"&gt;convert a single environment site&lt;/a&gt; into a multi-environment site.&lt;/p&gt;
&lt;p&gt;Once you've made the changes you want, you can copy the changes from staging to your production environment.&lt;/p&gt;
&lt;p&gt;WP Engine also allows you to copy changes from a staging environment of one site to another website. This means you can roll out updates or changes to all your sites without repeating the staging process for each site. However, this can get a bit complicated and isn't recommended for those new to WordPress.&lt;/p&gt;

&lt;h3&gt;Staging with Kinsta&lt;/h3&gt;
&lt;p&gt;Creating a staging site with Kinsta is quite easy. Access your Kinsta dashboard and select your site. Here, on the top right, you have the option to create a staging environment for your website. It takes around 10-15 minutes to create a staging site.&lt;/p&gt;

&lt;figure class="figure d-flex flex-column align-items-center"&gt;
    &lt;img src="https://migratecontent.com/images/Kinsta-WordPress-staging-1024x553.png" class="figure-img img-fluid rounded" alt="Kinsta WordPress staging" width="640" height="346"&gt;
&lt;/figure&gt;

&lt;p&gt;Once you refresh the page, you will see your staging details. You can make the changes you like to your staging site and then push them to your production environment. To do this, under the 'Staging Environment' tab, there's a 'Push Staging to Live' button. Simply click on it and all the changes will be made visible on your live site.&lt;/p&gt;
&lt;p&gt;There's no selective merge option here. So if you're pushing changes to live, be aware that all changes will be merged.&lt;/p&gt;
&lt;h2&gt;Final Thoughts&lt;/h2&gt;
&lt;p&gt;That's a wrap on backups and staging for your WordPress site. To summarize, hosts may offer free versions of backup and staging, but you're limited in terms of features and functionality. As your site grows bigger, you would need to upgrade to premium plans which are quite expensive. However, when you opt for a plugin like BlogVault, it's reasonably priced, gives you access to premium features, and above all, it works seamlessly.&lt;/p&gt;
&lt;p&gt;Whichever be your choice, make sure you can rely on your backup to work and be restored easily. Finally, always carry out changes in a staging environment before updating your live site. This will keep you out of trouble and ensure your site is always up and running.&lt;/p&gt;</description><category>backups</category><category>blog</category><category>blogvault</category><category>development</category><category>help</category><category>hosting</category><category>kinsta</category><category>staging</category><category>wordpress</category><category>wp engine</category><guid>https://migratecontent.com/wordpress-backups-and-staging-guide/</guid><pubDate>Tue, 11 Feb 2020 12:59:11 GMT</pubDate></item><item><title>Migrating Delicious Bookmarks to WordPress</title><link>https://migratecontent.com/migrating-delicious-bookmarks-wordpress/</link><dc:creator>Anthony Lopez-Vito</dc:creator><description>&lt;p&gt;Delicious is one of those services that few people know about but loved (and probably hated in equal measure) by those who use it. &lt;a href="https://del.icio.us/about"&gt;Their offering&lt;/a&gt; is easy to grasp: Delicious is a social bookmarking service that lets you &lt;em&gt;"Save, organize, and remember the links you find interesting or useful around the web."&lt;/em&gt; I'm sure you've been in a situation where you've tried to remember the source for a particular factoid or needed to cite an article but lost track of the link. The obvious place to save links is in the browser bookmarks but this quickly becomes unwieldy if, for example, you're doing research on lots of different topics. Unless you install bookmark syncing software, browser-based bookmarks are also cumbersome if you run different browsers and computers. I used Delicious to store thousands of links over the years, all of which where tagged and easy to call up when needed. They say in their about page, &lt;em&gt;"Delicious remembers so you don't have to. It's easy to build up a collection of links, essentially creating your own personal search engine."&lt;/em&gt; It was great at that and absolutely invaluable if, like me, you have a poor memory. Programmers, bloggers, researchers, anyone who needs to save a link for future recall needs something like Delicious. Founded in 2003, it's also a veteran in an industry where anything that lasts more than a couple of years is considered successful.&lt;/p&gt;

&lt;p&gt;&lt;img src="https://migratecontent.com/images/bookmarks-wordpress-migration-article-image.png" alt="Old book with bookmark for Bookmark to WordPress migration" width="800" height="425" class="aligncenter size-full wp-image-1806"&gt;&lt;/p&gt;

&lt;p&gt;Sadly, this glowing opening isn't to recommend the service. You'd think its longevity would be a sign of a rock-solid, mature platform but no: Delicious' loyal user-base has been rewarded with &lt;a href="https://gigaom.com/2011/09/28/oh-delicious-where-did-it-all-go-so-wrong/" title="Oh, Delicious — where did it all go so wrong?"&gt;outages, lost data and broken features&lt;/a&gt;. That people persisted despite years of problems shows just how useful a service it provides. When the site &lt;a href="https://www.lireo.com/delicious-social-bookmarking-service-back-again/" title="Delicious, the Social Bookmarking Service is Back, Again"&gt;went down again earlier this year&lt;/a&gt; (2016), I decided it was time to make a move. Unfortunately I couldn't find an alternative trustworthy enough for several years-worth of carefully curated bookmarks. Free web services are notorious for &lt;a href="https://www.wired.com/2009/01/magnolia-suffer/" title="Ma.gnolia Suffers Major Data Loss, Site Taken Offline"&gt;disappearing into a black hole&lt;/a&gt; with all your data. As the saying goes, you get what you pay for.&lt;/p&gt;

&lt;p&gt;After a long search, I began to realise there wasn't anyone out there who could be trusted. This isn't just Delicious and bookmark curation problem though. These past few years has shown that The Cloud hasn't lived up to its promise. Data breaches, surveillance, data collection, outages, and catastrophic meltdowns; we can't &lt;em&gt;really&lt;/em&gt; trust a third-party service, especially if they don't have a clear business model. I grudgingly conceded that cobbling together my own solution was the only option.&lt;/p&gt;

&lt;p&gt;The rest of this post describes my solution, why I chose WordPress and how you can convert your WordPress site to host a personal bookmarking service. This will be valuable even for those who've never used Delicious but would like a way to curate links.&lt;/p&gt;

&lt;h2&gt;Exporting the bookmarks&lt;/h2&gt;

&lt;p&gt;Before doing anything else, the bookmarks need to be in form that's easy to manipulate. Delicious had a feature to export all your links, tags and notes into a HTML file &lt;a href="https://msdn.microsoft.com/en-us/library/aa753582(v=vs.85).aspx"&gt;Netscape bookmark format&lt;/a&gt;. At the time of writing this has been 'temporarily disabled due to server load' (really, Delicious?). Fortunately I was in the habit of making frequent backups due to Delicious' unreliability so my export file was only a few weeks old. I threw together a quick Python script called DeliciousPy to scrape the file and save the results into a local MySQL database. Feel free to grab the source over on &lt;a href="https://gitlab.com/anthonylv/DeliciousPy"&gt;GitLab&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It was a one-use tool so a little rough and undocumented. (Sorry, it wasn't written with the intention of public release!) Anyone with basic Python knowledge should be able to easily figure out how it works. Essentially, I parse the Delicious export file using &lt;a href="http://www.tibonihoo.net/blog/en/"&gt;Thibauld Nion's&lt;/a&gt; Netscape bookmark parser that is part of his &lt;a href="https://github.com/tibonihoo/wateronmars"&gt;Water On Mars!&lt;/a&gt; project. Everything is then inserted into three MySQL database tables:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;bookmarks:&lt;/strong&gt; the table storing bookmark title, url, note, creation time and privacy flag.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;tags:&lt;/strong&gt; all the tags associated with the Delicious bookmarks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;tag_relationships:&lt;/strong&gt; the relationships between the bookmarks and tags.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After doing a &lt;code&gt;pip install&lt;/code&gt; to install the requirements, you run DeliciousPy with the command:
&lt;code&gt;$ ./deliciouspy.py -p /path/to/delicious/export_file.html&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Running the script exports:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Bookmark title&lt;/li&gt;
&lt;li&gt;URL&lt;/li&gt;
&lt;li&gt;Tags&lt;/li&gt;
&lt;li&gt;Note&lt;/li&gt;
&lt;li&gt;Created date&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Getting the Delicious bookmarks into a database opens up options for importing the data into a different platform. You can roll your own custom tool or use a content management system. I chose WordPress.&lt;/p&gt;

&lt;h2&gt;WordPress as a personal social bookmarking service&lt;/h2&gt;

&lt;p&gt;My wish list for a Delicious replacement was short:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Save links with accompanying notes.&lt;/li&gt;
&lt;li&gt;Tagging and search to easily call up previously saved links.&lt;/li&gt;
&lt;li&gt;Simple, bare-bones functionality free of unnecessary features.&lt;/li&gt;
&lt;li&gt;Set links to private for personal research or public for sharing.&lt;/li&gt;
&lt;li&gt;Avoid relying on a third-party service.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It didn't take me long to settle on WordPress. I already have expertise with importing data into WordPress from my &lt;a href="https://migratecontent.com/" title="MigrateContent: Drupal to WordPress migration service"&gt;Drupal to WordPress migration service&lt;/a&gt;. It's grown into a mature content management platform with a huge user and developer base, apparently powering &lt;a href="https://w3techs.com/blog/entry/wordpress-powers-25-percent-of-all-websites"&gt;25% of all websites&lt;/a&gt;. It has excellent documentation, can run on a standard hosting package, has a simple user-interface and a flexible taxonomy system. The code is open source so if you self-host the site, you won't run into the third-party service problems of getting locked out of your data. WordPress has all the components for a home-brew bookmarking service.&lt;/p&gt;

&lt;h3&gt;My Bookmarks plugin&lt;/h3&gt;

&lt;p&gt;I'd originally hoped to avoid building my own plugin but none of those in the &lt;a href="https://wordpress.org/plugins/" title="WordPress Plugin Directory"&gt;WordPress Plugin Directory&lt;/a&gt; suited my needs. Most were too feature-packed and I wanted something lightweight: just have some way of saving and tagging links for later retrieval. Putting together simple bookmark storage isn't difficult: 'bookmarks' can be nothing more than a post with a single custom field to store the URL. To keep them separate from standard blog posts, I created a custom bookmark content type and packaged it into a plugin called &lt;strong&gt;&lt;em&gt;My Bookmarks&lt;/em&gt;&lt;/strong&gt;. (I'm not very imaginative when naming things.)&lt;/p&gt;

&lt;p&gt;Delicious has a social bookmarking aspect that lets you publish your links, follow other users and discover pages those in your network have saved. Social bookmarking wasn't compelling for me so I didn't attempt to include this functionality. In my opinion, publishing the links on a blog is social enough and any anyone who wants to 'follow' can subscribe to the RSS feed built into WordPress.&lt;/p&gt;

&lt;p&gt;Bookmark sharing id controlled through the normal WordPress &lt;em&gt;Visiblity&lt;/em&gt; setting. Set to &lt;em&gt;Public&lt;/em&gt; so the bookmark gets posted on your blog; set to &lt;em&gt;Private&lt;/em&gt; so it's visible only after logging in to WordPress.&lt;/p&gt;

&lt;p&gt;One great thing about Delicious was a handy bookmarklet that allowed you bookmark your browser's current open page. Rather annoyingly, this feature broke for me at some point after it was acquired by one of its &lt;a href="https://en.wikipedia.org/wiki/Delicious_(website)#History"&gt;many owners&lt;/a&gt;. I implemented this functionality in the form of a WordPress-style &lt;em&gt;Press This&lt;/em&gt; bookmarklet. Code from the now seemingly abandoned &lt;a href="https://github.com/jchristopher/linkmarklet" title="Bookmarklet plugin aimed at rapid linkblogging"&gt;Linkmarklet plugin&lt;/a&gt; by &lt;a href="http://mondaybynoon.com"&gt;Jonathan Christopher&lt;/a&gt; does most of this work.&lt;/p&gt;

&lt;h2&gt;Experience so far&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;&lt;em&gt;My Bookmarks&lt;/em&gt;&lt;/strong&gt; plugin hasn't been published to the WordPress Plugin Directory as of now. I'm still trialling it to make sure everything works as expected before releasing but you're welcome to grab the source and tinker with it for your own needs. &lt;em&gt;Note: As of December 2016, the My Bookmarks plugin is temporarily hosted over on &lt;a href="https://gitlab.com/anthonylv/my-bookmarks" title="My Bookmarks: a WordPress social bookmarking plugin"&gt;GitLab&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Currently the plugin is installed on my internal Wordpress-based Knowledge Management System on my local network. It serves up thousands of bookmarks from around 10 years worth of links. I replicated everything that made Delicous so useful for me without all the drawbacks of a third-party service. So far so good. The bookmarks that I've spent years curating are now fully under my control—and under my responsibility. Backups are still important but bookmarks are now included with my usual automated WordPress database dumps. All-in-all, I think it was a good move to finally migrate from Delicious.&lt;/p&gt;

&lt;div id="footnotes"&gt;Book photo by Katia Grimmer-Laversanne from &lt;a href="http://www.freeimages.com/photo/bookmark-1526985"&gt;freeimages.com&lt;/a&gt;&lt;/div&gt;</description><category>blog</category><category>bookmarks</category><category>curation</category><category>delicious</category><category>export</category><category>links</category><category>migration</category><category>plugin</category><category>python</category><category>wordpress</category><guid>https://migratecontent.com/migrating-delicious-bookmarks-wordpress/</guid><pubDate>Wed, 30 Nov 2016 11:38:07 GMT</pubDate></item><item><title>Drupal to WordPress migration table mapping</title><link>https://migratecontent.com/drupal-to-wordpress-migration-table-mapping/</link><dc:creator>Anthony Lopez-Vito</dc:creator><description>&lt;p&gt;Following on from &lt;a href="https://migratecontent.com/drupal-to-wordpress-migration-sql-queries-explained/"&gt;Drupal to WordPress migration explained&lt;/a&gt;, this post documents the table mappings for a &lt;a href="https://migratecontent.com/drupal-to-wordpress-migration-service/" title="Drupal to WordPress migration service"&gt;site migration&lt;/a&gt; from Drupal 6.x to WordPress 3.x.&lt;/p&gt;
&lt;p&gt;To read the mapping, you look up the Drupal table on the left listing the fields we use for a migration. Directly to its right is the WordPress table with the corresponding field in the same row. So for example, the &lt;em&gt;nid&lt;/em&gt; in Drupal’s &lt;em&gt;node&lt;/em&gt; table is exported to the &lt;em&gt;id&lt;/em&gt; field in the WordPress &lt;em&gt;wp_posts&lt;/em&gt; table.&lt;/p&gt;
&lt;p&gt;I have listed all the fields used in the query. If a Drupal field shows no mapping in the WordPress table, it is being used to match entries in another table for a join. Here we use the &lt;em&gt;vid&lt;/em&gt; field in &lt;em&gt;node&lt;/em&gt; and &lt;em&gt;node_revisions&lt;/em&gt; for an INNER JOIN.&lt;/p&gt;

&lt;h2&gt;Table mapping for WordPress wp_posts&lt;/h2&gt;
&lt;table class="table table-bordered table-hover"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Drupal 6.x&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;WordPress 3.x&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Notes&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;node&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;wp_posts&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;nid&lt;/td&gt;
&lt;td&gt;id&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;id&lt;/td&gt;
&lt;td&gt;post_author&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;created&lt;/td&gt;
&lt;td&gt;post_date&lt;/td&gt;
&lt;td&gt;Create date from UNIX timestamp&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;title&lt;/td&gt;
&lt;td&gt;post_title&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;changed&lt;/td&gt;
&lt;td&gt;post_modified&lt;/td&gt;
&lt;td&gt;Create date from UNIX timestamp&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;type&lt;/td&gt;
&lt;td&gt;post_type&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;status&lt;/td&gt;
&lt;td&gt;post_status&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;vid&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;node_revisions&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;body&lt;/td&gt;
&lt;td&gt;post_content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;teaser&lt;/td&gt;
&lt;td&gt;post_excerpt&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;vid&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;node&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;url_alias&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;nid&lt;/td&gt;
&lt;td&gt;dst&lt;/td&gt;
&lt;td&gt;post_name&lt;/td&gt;
&lt;td&gt;If dst field is NULL, use nid&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;src&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;to_ping&lt;/td&gt;
&lt;td&gt;Whitespace string&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;pinged&lt;/td&gt;
&lt;td&gt;Whitespace string&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;post_content_filtered&lt;/td&gt;
&lt;td&gt;Whitespace string&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;h3&gt;Query&lt;/h3&gt;
&lt;div class="code"&gt;&lt;pre class="code sql"&gt;
REPLACE INTO wordpress.wp_posts (&lt;br&gt;
		id,&lt;br&gt;
		post_author,&lt;br&gt;
		post_date,&lt;br&gt;
		post_content,&lt;br&gt;
		post_title,&lt;br&gt;
		post_excerpt,&lt;br&gt;
		post_name,&lt;br&gt;
		post_modified,&lt;br&gt;
		post_type,&lt;br&gt;
		post_status,&lt;br&gt;
		to_ping,&lt;br&gt;
		pinged,&lt;br&gt;
		post_content_filtered)&lt;br&gt;
	SELECT DISTINCT&lt;br&gt;
		n.nid ‘id’,&lt;br&gt;
		n.uid ‘post_author’,&lt;br&gt;
		DATE_ADD(FROM_UNIXTIME(0), interval n.created second) ‘post_date’,&lt;br&gt;
		r.body ‘post_content’,&lt;br&gt;
		n.title ‘post_title’,&lt;br&gt;
		r.teaser ‘post_excerpt’,&lt;br&gt;
		IF(a.dst IS NULL,n.nid, SUBSTRING_INDEX(a.dst, ‘/’, -1)) ‘post_name’,&lt;br&gt;
		DATE_ADD(FROM_UNIXTIME(0), interval n.changed second) ‘post_modified’,&lt;br&gt;
		n.type ‘post_type’,&lt;br&gt;
		IF(n.status = 1, ‘publish’, ‘private’) ‘post_status’,&lt;br&gt;
		‘ ‘,&lt;br&gt;
		‘ ‘,&lt;br&gt;
		‘ ‘&lt;br&gt;
	FROM drupal.node n&lt;br&gt;
	INNER JOIN drupal.node_revisions r USING(vid)&lt;br&gt;
	LEFT OUTER JOIN drupal.url_alias a&lt;br&gt;
		ON a.src = CONCAT(‘node/’, n.nid)&lt;br&gt;
		WHERE n.type IN (&lt;br&gt;
			/* List the content types you want to migrate */&lt;br&gt;
			‘page’,&lt;br&gt;
			‘story’,&lt;br&gt;
			‘blog’,&lt;br&gt;
			‘video’,&lt;br&gt;
			‘forum’,&lt;br&gt;
			‘comment’);
&lt;/pre&gt;&lt;/div&gt;

&lt;h2&gt;Table mapping for WordPress terms&lt;/h2&gt;
&lt;p&gt;This table mapping exports the Drupal terms into WordPress.&lt;/p&gt;
&lt;table class="table table-bordered table-hover"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;Drupal 6.x&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;WordPress 3.x&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Notes&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;term_data&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;wp_terms&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;tid&lt;/td&gt;
&lt;td&gt;term_id&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;name&lt;/td&gt;
&lt;td&gt;name&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;name&lt;/td&gt;
&lt;td&gt;slug&lt;/td&gt;
&lt;td&gt;Make lower case and convert spaces to underscores&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;vid&lt;/td&gt;
&lt;td&gt;term_group&lt;/td&gt;
&lt;td&gt;Not used in a default WordPress installation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;term_data&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;wp_term_taxonomy&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;tid&lt;/td&gt;
&lt;td&gt;term_taxonomy_id&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;tid&lt;/td&gt;
&lt;td&gt;term_id&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;taxonomy&lt;/td&gt;
&lt;td&gt;String: ‘post_tag’ or ‘category’&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;description&lt;/td&gt;
&lt;td&gt;description&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;parent&lt;/td&gt;
&lt;td&gt;0 (No parent)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;In the &lt;a href="https://codex.wordpress.org/WordPress_Taxonomy"&gt;WordPress Taxonomy documentation&lt;/a&gt;, &lt;em&gt;“term_group is a means of grouping together similar terms.”&lt;/em&gt; During a standard migration, the WordPress term_group is set to the Drupal vocabulary ID, which seems to make sense. Nevertheless, a default WordPress installation does not actually use the value for anything. It may have been included by the developers for future expandability or use by plugins.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;term_group=0&lt;/em&gt; is the default value when creating a term using the Drupal user interface.&lt;/p&gt;
&lt;p&gt;Below, we associate posts with the newly migrated terms.&lt;/p&gt;
&lt;table class="table table-bordered table-hover"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;Drupal 6.x&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;WordPress 3.x&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;term_node&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;wp_term_relationships&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;nid&lt;/td&gt;
&lt;td&gt;object_id&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;tid&lt;/td&gt;
&lt;td&gt;term_taxonomy_id&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;h2&gt;Table mapping for WordPress users&lt;/h2&gt;
&lt;p&gt;This maps Drupal user export to WordPress.&lt;/p&gt;
&lt;table class="table table-bordered table-hover"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;Drupal 6.x&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;WordPress 3.x&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Notes&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;users&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;wp_posts&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;uid&lt;/td&gt;
&lt;td&gt;ID&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;name&lt;/td&gt;
&lt;td&gt;user_login&lt;/td&gt;
&lt;td&gt;Format to lowercase, replace spaces with underscores&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;pass&lt;/td&gt;
&lt;td&gt;user_pass&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;name&lt;/td&gt;
&lt;td&gt;user_nicename&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;mail&lt;/td&gt;
&lt;td&gt;user_email&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;created&lt;/td&gt;
&lt;td&gt;user_registered&lt;/td&gt;
&lt;td&gt;Formatted from UNIX time&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;name&lt;/td&gt;
&lt;td&gt;display_name&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;user_status&lt;/td&gt;
&lt;td&gt;Whitespace string&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;user_activation_key&lt;/td&gt;
&lt;td&gt;Set to 0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
 &lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;h2&gt;Table mapping for WordPress user meta values&lt;/h2&gt;
&lt;p&gt;User information like capabilities and roles in the &lt;em&gt;wp_usermeta&lt;/em&gt; table.&lt;/p&gt;
&lt;table class="table table-bordered table-hover"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;users&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;wp_usermeta&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;uid&lt;/td&gt;
&lt;td&gt;user_id&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;meta_key&lt;/td&gt;
&lt;td&gt;Set to string e.g. ‘wp_capabilities’&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;meta_value&lt;/td&gt;
&lt;td&gt;Set to string e.g. ‘a:1:{s:6:”author”;s:1:”1″;}’&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;More information about the settings for appropriate &lt;em&gt;meta_key&lt;/em&gt; and &lt;em&gt;meta_value&lt;/em&gt; can be found in the WordPress Codex:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://codex.wordpress.org/Roles_and_Capabilities"&gt;Roles and Capabilities&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://codex.wordpress.org/User_Levels"&gt;User Levels&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Node authors and comment authors&lt;/h2&gt;
&lt;p&gt;Drupal stores both node authors and comment authors in the &lt;em&gt;users&lt;/em&gt; table. WordPress handles things differently. Page and post authors are stored in the &lt;em&gt;wp_users&lt;/em&gt; table but comment authors are stored in &lt;em&gt;wp_comments&lt;/em&gt; together with the comment data.&lt;/p&gt;

&lt;h2&gt;Table mapping for WordPress comments&lt;/h2&gt;
&lt;table class="table table-bordered table-hover"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;Drupal 6.x&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;WordPress 3.x&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Notes&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;comments&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;wp_posts&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;cid&lt;/td&gt;
&lt;td&gt;comment_ID&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;nid&lt;/td&gt;
&lt;td&gt;comment_post_ID&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;timestamp&lt;/td&gt;
&lt;td&gt;comment_date&lt;/td&gt;
&lt;td&gt;Converted from UNIX timestamp&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;comment&lt;/td&gt;
&lt;td&gt;comment_content&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;pid&lt;/td&gt;
&lt;td&gt;comment_parent&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;name&lt;/td&gt;
&lt;td&gt;comment_author&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;mail&lt;/td&gt;
&lt;td&gt;comment_author_email&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;homepage&lt;/td&gt;
&lt;td&gt;comment_author_url&lt;/td&gt;
&lt;td&gt;Truncated to WordPress limit of 200 chars&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;status&lt;/td&gt;
&lt;td&gt;comment_approved&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;Comment authors&lt;/h2&gt;
&lt;p&gt;A note about the different ways Drupal and WordPress store comment author information: Drupal stores comment authors in its &lt;em&gt;users&lt;/em&gt; table alongside site users like node authors. In WordPress, comment authors are stored in its &lt;em&gt;wp_comments&lt;/em&gt; together with the comment data. WordPress comment authors are not entered into the &lt;em&gt;wp_users&lt;/em&gt; table.&lt;/p&gt;</description><category>blog</category><category>drupal</category><category>migration</category><category>scripts</category><category>sql</category><category>wordpress</category><guid>https://migratecontent.com/drupal-to-wordpress-migration-table-mapping/</guid><pubDate>Sat, 05 Jul 2014 02:07:29 GMT</pubDate></item></channel></rss>