Automattic has announced that Tumblr blogs will be moving all of its blogs to the WordPress backend. Tumblr will slowly be migrating over half a billion blogs over to WordPress which is a tricky and lengthy process but doable.
In an official blog post, Automattic has put out official statements clarifying Tumblr’s migration. Tumblr is stated to remain the same as it used to be. Users will not notice a difference on the outside. However, the backend operation will be transferred over to WordPress. There will be changes in terms of internal operations.
This transfer of Tumblr blogs to WordPress is expected to make it easier for blogs to be shared across platforms. Tumblr will be run on a solid infrastructure backed by WordPress and it will thus benefit from an open-source project such as WordPress. Furthermore, the blog post also stated that WordPress would also benefit from this transfer. WordPress will have the advantage of Tumblr’s tools and creativity that the teams invest in the site.
Tumblr Blogs After Automattic Acquisition in 2019
Automattic is the parent company of both Tumblr and WordPress. The company acquired Tumblr back in 2019 for only $3 million. This acquisition came six years after Yahoo acquired Tumblr for $1.1 billion which is a drastic amount compared to the $3 million that Automattic spent on buying Tumblr. However, Automattic’s CEO, Matt Mullenweg believed that Tumblr’s future still had promise. Since Automattic acquired Tumblr, the company has worked towards improving the blogging site and bringing Tumblr back to its glory days.
However, even with Mullenweg’s optimistic outlook, Tumblr kept losing money at a whopping $30 million yearly. Due to Tumblr’s losses, Mullenweg had to transfer most of Tumblr’s teams to Automattic in 2023. Additionally, Tumblr employees had also been laid off. Tumblr continues to generate revenue through ads, subscriptions and other digital services.
Suggested:
WordPress Superhero Challenge Opened by Wordfence.
WordPress Tracks Down XSS Vulnerability- Users To Update To 6.5.2.