Migrate TYPO3 or move to Drupal or WordPress or Joomla?

Today with such huge leap in the changes to TYPO3, people are really moving over to WordPress and Drupal. There is a haphazard move to migrate to Druapl and WordPress. People are cashing in, and we at SCWEBS as a solution expert are not really happy about this extra bill. Financially this is extremely good, for an agency like ours.

We can just cash out by suggesting alternate solution, and justfy extra costs, and keep our company runing happy at the cost of my client’s money!

Is this really justified?


There are more than 4 lac websites that are still running on TYPO3 version 4.5.x and TYPO3 version 4.6.x.

One of the major change was the move from PiBase to ExtBase. Developers were not ready to move, clients were not ready to move. And the real fact that whenver there is a change – no one really wants to be ready. But the one who makes the move will be the smart person.

Some of the large enterprises and NGOs are already migrating from TYPO3 4.x or TYPO3 6.x to the latest TYPO3 version. But the main debate was whether we should really stick to TYPO3?

Several companies have already moved from TYPO3 to other options like Drupal, Joomla and WordPress. Was it really a cost saving smart move? I don’t think so.

I have been working on Content Management Systems (CMS) since almost 18 years or more from now. That is as a student, I had been fond of Content Management Systems (CMS). When I saw Drupal, WordPress and Joomla I had even started writing my own CMS system during those times.

When I met TYPO3, I was totally surprised that this Content Management System (CMS) can take over everything. TYPO3 was not framed behind PiBase or ExtBase, but it came forward with a beautful idea from the king Kasper Skårhøj. His main ideas helped build this extremely flexible Enterprise class Content Management System (CMS) from day one!!!. TYPO3 surely needs time to learn, but one learnt there is no going back. You can make it work like a Blog like WordPress, as an E-Commerce system like Magento, WooCommerce, PrestaShop or anything out of those 100+ choices, TYPO3 can be a Comunity portal like Drupal’s strong features.

TYPO3 could become anything, and even today when I re-learnt Drupal and WordPress, I am not happy with the options. WordPress and Drupal surely do excel, but if you chose TYPO3 once, I do not see a point why one should move out.

But such a move will surely cost on a long run, because in-spite of learning Drupal, WordPress and other ssytems I am not happy with these systems. One can argue that this is my individual opinion, but trust me on a real long run – the cost of choosing other systems will be learnt.

Today at SCWEBS we still use TYPO3 as our main expert area, and when one needs a real blog, we still do prefer WordPress. But if it is very simple blog like feature, TYPO3 is all we prefer. For E-Commerce WooCommerce or Prestashop and we do prefer a TYPO3 based shop like tt_product on several occasions. Drupal or Joomla almost never come into picture untill and unless a customer really wants to get it done by us.

In many cases, we have built a totally custom solution using Symfony and Laravel but we are proud that till date have never moved a TYPO3 customer out. I feel that migrating to ExtBase and TYPO3 Version 9 is far easier than moving over to Drupal.

If you want to migrate your site to WordPress or Drupal, contact us, we will personally help you out. I will show why TYPO3 is still better than the rest. There are 100+ reasons and areas where TYPO3 excels.

If you are still running your website on one of the TYPO3 versions like TYPO3 version 3.8, TYPO3 version 4.5 or TYPO3 version 4.6, TYPO3 version 6.2 LTS then we suggest it is time to migrate to newer TYPO3 version.

TYPO3 is quite secure, and we can justify it. We still kept some of our site on versin 4.x to analyze how attacks happen, and to what level. Today, on one of our 4.5 site, the site goes down and comes back up within 10 minutes, all by itself. The hackers are trying twice every day to get in, and succeed to a level, but they can’t get much deeper. We are watching what all they can do. They could not do much harm as of now… but we can’t sayfor how long. We are not such big security experts like our friends in TYPO3 security team. So our advice – migrate before it is too late.

These older versions are slowly getting older, and they may soon be hacked by a smart thief. By now, agencies are all well prepared to handle TYPO3 migrations, and these days costs are quite lower too. If you are an agency with many TYPO3 sites that needs migration, we can help with several strategies to lower the costs much further.

If you have a TYPO3 migration query, do get in touch with us. We are curiously waiting.

Getting back after a long gap


SCWEBS Info Solutions PVT LTD, is already 3 years old Indian Company. The journey through these years had been really tough and challenging. Together with my experience in Chandan Web Solutions, our total TYPO3 expertise rises to 10+ years. I was involved with TYPO3 since version 3.8, but within 6 months of knowing TYPO3 the version 4.0 came in.

Since beginning we just had TYPO3 as our main and core expertise. It is during the year 2016 till date, that we started gathering knowledge in several other areas. Our main goal was not just to have a peek into these new technologies, but to have in-depth subject expertise in what we learn.

On one hand we learnt new CMS systems like Drupal, WordPress, and Joomla. On the other hand we explored some of the core PHP frameworks like Symfony, Laravel and CakePHP.

E-Commerce systems like WooCommerce and Prestashop remained on top of our pick list Finally Magento was completely dropped off from our palette.

Quality always came at a price, and we always had a good struggle to prove ourselves on our prices. Initially it had been extremely tough time convincing our European friends that we could really work on TYPO3!

Our TYPO3 journey started with TYPO3 version 3.8. When we started working on TYPO3 4.x I met Francois Suter. This was never possible without the help of my TYPO3 Guru Francois Suter. Who carefully carved me and gave in-depth ideas about TYPO3.

Today, we are working hard to migrate nearly 20+ websites from TYPO3 version 4.5 and TYPO3 version 4.6. This list also had two peculiar website that ran TYPO3 version 3.8 which is already migrated to TYPO3 version 9. One peculiar issue that we are facing is with RealURL, which we must soon overcome.

Along with these, we are also working on a good WooCommerce based solution, and a custom WordPress integration as well. Product development is also on the card, which is soon going to kick off.

Year 2018 is getting busier, and we are happy that we are getting back on. Our site had been helpful for TYPO3 community for quite many years. Since last few years this had changed. I am also planning to write more on technical side. This time the concetration will be on my entire technical knowledge, and not just on TYPO3. There is also an article waiting for a simple step to migrate TYPO3 to version 9.

We are also updating our website with a new year 2018 theme. This new site, which is all colorful, is going to showcase our TYPO3 skills, as well as our new expert areas.



Customize Templavoila new content element wizard

templavoila.wizards.newContentElement {
# Activate tabs for new content element wizard in TV
renderMode = tabs

wizardItems.common.elements.tx_custom_bigimage {
icon = Images/Bigimage.png
title = BG Image
description = BG Image
tt_content_defValues {
CType = tx_custom_bigimage
wizardItems.common.show := addToList(tx_custom_bigimage)

Where tx_custom_bigimage is custom content type. we need to add this code in pagetsconfig of root page.

Please refer to screenshot for more info.New content Element Wizard

Typoscript snippet for getting parent title, based on selected Templavoila Template Object


5 = TEXT
5 {
#first check with tx_templavoila_to
ifEmpty.cObject = TEXT
ifEmpty.cObject {
data = leveltitle:-2
stdWrap.case = upper
if {
value = 34
isInList.data = levelfield:-1, tx_templavoila_to, slide
#then check with tx_templavoila_next_to
ifEmpty.ifEmpty.cObject < .ifEmpty.cObject
ifEmpty.ifEmpty.cObject = TEXT
ifEmpty.ifEmpty.cObject.if.isInList.data = levelfield:-1, tx_templavoila_next_to, slide

noTrimWrap = || – |