Good content.
A fresh
perspective.
Your content and customer relationships are valuable, even when the system behind them can no longer keep up. We assess what should stay, what holds you back and which next step makes business sense.
Discuss migrationFind a way forward.
With a transparent proposal.
You do not need to know the name of your next platform yet. What matters is what works today, which content and processes must stay, and what costs time or money. We use that to compare ongoing operation, modernization and migration.
Clarity before the change
We record versions, extensions, custom functions, access and export options. You receive a risk assessment and a comparison: continue support, upgrade or migrate. This includes priorities, open questions and a defined implementation scope.
Learn moreContent with a maintainable future
We plan data migration, a new content structure, replacement functions and redirects. A trial import makes effort and limitations visible. Implementation, acceptance and the switch are proposed on that basis, with additional services shown separately.
Learn moreSupport with clear tasks
Updates, backups, functional tests and editorial support receive an agreed framework. You know which work is included, when additional effort arises and who is responsible for problems.
Learn morePrice and timing depend on the accessible setup, desired functions and agreed scope. The assessment may also show that targeted modernization makes more business sense than a complete migration.
‘It still works’ is
not a maintenance plan.
A website can be available while relying on technology that is no longer supported.
Known vulnerabilities in a CMS, modules or libraries can, depending on the flaw, allow unauthorized access, manipulated content or data leaks. When a version is no longer maintained, the normal route to a fix may be missing. PHP, Python, .NET, databases and the operating system therefore belong in the assessment too.
Limited adoption does not automatically make a system insecure. A major brand does not make an installation left unmaintained for years secure either. Actual versions, available security fixes, installed extensions and someone responsible for changes are decisive.
A backup helps recovery; it does not close a vulnerability. A firewall can provide additional protection but does not replace supported software. When updates are blocked, a specific modernization or replacement plan is needed.
No maintained version
We check end of support and the upgrade path. Unsupported modules are replaced, functions simplified or content moved to another platform.
No one takes responsibility
Missing documentation, unclear license ownership and lost handovers are addressed. A technical takeover needs clear access and responsibilities.
Suspected attack
Where compromise is suspected, scope and immediate action are clarified first. Malicious code and unknown legacy problems must not move into the new system with the content.
Does your website have an urgent problem?
Describe the outage, error or anomaly here. We clarify the current state and next steps first.
A portal is more
than a collection of pages.
DNN is a CMS and portal system in the .NET ecosystem, not merely a blogging tool. The platform continues to develop. For old installations, the version, modules, custom extensions and Windows / IIS environment matter.
For migration, we record the page structure, content, files, forms and protected areas. User roles, memberships and custom data modules need separate mapping. Functions that work differently in the target system are described anew in business terms.
DNN's security policy generally does not provide hotfix releases for earlier platform versions. Postponing an update is therefore not a lasting substitute for sustainable operation.
Data flows & .NET integrationsThe project remains active.
The old version does not.
django CMS is not generally obsolete. The old 3.11 series reached its announced end of support in April 2026. Newer series continue to develop. The CMS, Django, Python and additional packages must be considered together.
In application-specific projects, functions often sit outside the CMS too: data models, search, forms and integrations. Exporting only the pages would overlook these dependencies.
We compare updating the existing system with migration. If the Python application remains useful, modernization may be the better route. For a mainly editorial website, a simpler CMS structure can reduce future effort.
Is your system unusual?
Your content is worth it.
We assess migrations from both established and less common CMS, blog, portal and store systems. The overview covers 92 source systems or product families.
Blogs & editorial archives11 systems
- WordPress
- Serendipity
- Textpattern
- b2evolution
- Movable Type
- Nucleus CMS
- PivotX
- LifeType
- Geeklog
- Apache Roller
- Ghost
Traditional & flexible website CMS platforms21 systems
- Joomla
- TYPO3
- Drupal
- Contao
- REDAXO
- CMS Made Simple
- MODX
- ProcessWire
- Concrete CMS
- Silverstripe CMS
- October CMS
- Winter CMS
- Craft CMS
- ExpressionEngine
- Kirby
- Statamic
- Grav
- GetSimple CMS
- WebsiteBaker
- WBCE CMS
- CMSimple
Portals & older system families14 systems
- Mambo
- PHP-Nuke
- PostNuke
- Zikula
- XOOPS
- ImpressCMS
- e107
- PHP-Fusion
- DNN / DotNetNuke
- Umbraco
- Kentico / Xperience
- Sitefinity
- Orchard CMS
- Orchard Core
Python & application-focused CMS platforms7 systems
- django CMS
- Wagtail
- Plone
- Mezzanine
- Alchemy CMS
- Refinery CMS
- Radiant
Enterprise platforms10 systems
- OpenCms
- Jahia
- Magnolia
- dotCMS
- CrafterCMS
- Ametys
- FirstSpirit
- CoreMedia
- Adobe Experience Manager
- OpenText Web CMS
Headless CMS platforms & content services7 systems
- Strapi
- Directus
- Payload
- Contentful
- Storyblok
- Sanity
- Prismic
Website builders & hosted websites7 systems
- Wix
- Squarespace
- Webflow
- Jimdo
- IONOS MyWebsite
- Blogger
- Tumblr
Stores & commerce platforms11 systems
- PrestaShop
- WooCommerce
- Magento Open Source
- Adobe Commerce
- OpenCart
- Shopware
- osCommerce
- xt:Commerce
- Gambio
- Zen Cart
- Shopify
Wikis & knowledge resources4 systems
- MediaWiki
- DokuWiki
- Tiki
- MoinMoin
Mentioning a system does not mean it is obsolete or that every version can automatically be migrated in full. Accessible data, export rights, extensions and the intended destination are decisive. We can also assess custom development and systems not listed, using the specific setup.
Discuss your existing systemYour annual bill
deserves an explanation.
A good CMS can still be expensive within an unsuitable support model.
Craft CMS is a flexible system for structured content. If your Craft website's annual costs are rising, we first separate vendor licenses and update entitlement from plugin fees, hosting, agency services and custom development.
Craft Solo allows one user account, Team up to five and Pro unlimited user accounts. Pro therefore does not automatically charge every additional person as a separate CMS license. For paid licenses, using the installed version and renewing for updates or developer support are different matters. Plugin terms may apply separately.
An agency package can cover useful services: tested updates, recovery, monitoring or agreed response times. Pricing becomes problematic when scope and value are unclear, or every small change requires significant effort again. We examine services and invoice items rather than blaming the product name for costs.
Alternatives may include a simpler Craft installation, another support model or migration to a suitable CMS. Custom fields, relationships, languages, media and existing Twig templates are assessed separately. Templates cannot simply be transferred unchanged to every target system.
More accounts. More content.
But what additional value?
On some platforms, additional editorial accounts, roles, websites, languages or higher API and storage limits change the plan. On others, costs mainly arise from development and operation. We calculate using your actual usage scenario, including the next stage of growth.
A fair comparison requires both options to cover the same needs: necessary functions, reliable maintenance, editors' time and accessible support. A cheaper plan helps little if your team has to make up for missing functions manually every month.
- Licenses & usage
- Plan, accounts, roles, projects, extra modules and expected volumes. Which limit triggers the next price increase?
- Operation & support
- Hosting, backups, tests, monitoring, included hours and additional rates. What is a response, and what is a promised resolution?
- Internal work & transition
- Editing, duplicate maintenance, data cleanup, training, parallel operation and replacement. Switching also takes effort.
When does
a platform change pay off?
Compare total costs with the same service scope. Enter all amounts on the same basis, for example consistently excluding VAT.
Your calculation starts
with your existing setup.
Include licenses, modules, hosting, support and internal working time in annual costs. Unknown items should be clarified before deciding.
A simplified comparison with constant annual costs, without discounting, price increases or quantified outage risks. It does not replace an individual offer. Security, functions and support quality remain separate decision criteria.
Copying text
is rarely enough.
An old blog can contain years of specialist work. We plan the migration so it becomes a usable resource in the new system.
- Posts & relationships: Titles, content, publication dates, authors, categories, tags, comments and language variants are mapped to the target model.
- Media & files: Images, downloads, captions and internal references are checked. Old file paths and embedded content often need their own rules.
- URLs & discoverability: Important addresses, metadata and redirects are planned. Content no longer needed receives a deliberate decision instead of a blanket redirect to the home page.
- Accounts & functions: Roles, approvals, protected areas and forms are reproduced or reorganized. Password hashes are not always transferable; a secure reset process may be needed.
- Store data: Products, variants, customers and order history need their own migration plan. Payment data is not copied without assessment.
We use suitable exports, approved APIs or agreed database access. Where structured export is unavailable, we assess a controlled transfer of accessible content. Unavailable functions, private data or missing original files cannot be reconstructed at will from that.
A planned transition.
With someone who stays afterwards.
Clarify the setup & destination
We record what must stay, what can go and which difficulties should disappear. Versions, data, URLs, integrations and licensing are documented.
Try it with real content
A representative trial import shows how text, special characters, images, relationships and variants arrive. Exceptions become visible before the entire collection moves.
Prepare implementation & acceptance
New structures and functions are developed in a separate environment. We check counts, mappings, samples and key processes with your team.
Make a controlled switch
The content freeze, final data transfer, domain or DNS changes and a possible maintenance window are agreed. Backups, rollback and owners are defined beforehand.
Take on follow-up checks & support
Redirects, forms, orders and important pages are checked after the switch. Only then is the old operation retired in a controlled way. Documentation and ongoing maintenance belong in the handover.
Questions we
clarify first.
Does every older CMS need replacing?
No. A maintained version, useful functions and a viable technical foundation can support continued operation or an upgrade. We recommend a change where value, risks and total costs justify it.
Do you migrate unusual or custom blog systems too?
Yes, we explicitly assess these setups. Accessible content, data structure and required functions matter. A trial migration lets us define a reliable scope; a blanket completeness promise before assessment would not be responsible.
Is open source automatically cheaper?
No. Removing license costs can help, but hosting, modules, tests, security updates and support remain. We compare the entire operation and your team's time.
Will search engine rankings be preserved?
Rankings cannot be guaranteed. We consider important content, old URLs, redirects, metadata, internal links and technical indexability. Changes are monitored after the switch.
Can the old website stay online during the work?
The new solution is often built in parallel. The final data synchronization may need an agreed content freeze or maintenance window. For a security incident, immediate protection must be assessed separately.
What do you need for an initial assessment?
The website address, platform name and preferably its version, your main problems and a rough overview of recurring costs. Passwords or unredacted confidential documents should not go in an initial email; we agree secure exchange separately.