Why you need to migrate
Why do I need to migrate my website?
We will no longer support Isomer Classic as it’s reaching its end of life. To continue hosting your website with us, you will be moving to Isomer Next, which is an upgraded version of Isomer that we’ve been building since 2024.
Why are you not supporting Isomer Classic anymore?
We are moving to a single platform (Isomer Next) so that we can focus our resources to provide the best editing experience and produce better sites. Classic was built 6 years ago using older technologies. This slows down our abilities to make improvements to your editing experience and your sites.
Is there a deadline?
Yes, Isomer Classic will reach its end of life in December 2026. To ensure every site has a smooth transition, the final wave of migrations will begin in September 2026.
Rest assured that you do not need to wait till then. The move to Isomer Next is intentionally designed to be fast and painless, and starting earlier gives you more time to verify that your content is good to go. Our team will support you throughout this process, so the migration should feel like a simple lift-and-shift upgrade rather than a big move.
Differences between Isomer Classic and Next
What are the differences between Classic and Next? How is Next better?
Built on modern technologies
Isomer Next is built on a modern framework. This means that your websites are more future-proof and secure. It also helps us introduce new features for you at a faster speed.
Intuitive builder
The new site builder for Isomer Next (called Isomer Studio) provides a drag-and-drop editing experience. You don’t need to know markdown or coding (HTML/CSS) to build pages.
Variety of blocks
Isomer Next comes with pre-baked blocks so you can express your content without having to design anything.
DSS (Digital Service Standards) compliant
All of our blocks are built to be compliant with DSS. We actively monitor accessibility reports to make sure that any base features we provide are accessible out-of-the-box.
Feature | Isomer Classic | Isomer Next |
Technology stack | Jekyll, React.js | Next.js |
Website builder | Markdown/HTML | Drag-and-drop |
Built with DSS compliance | ❌ | ✅ |
Page-level publishing | ❌ | ✅ |
How will security be handled?
All Isomer Next sites are IM8 compliant (low-risk cloud). For SSP submission, you can go ahead to select Isomer’s low-risk template at https://docs.standards.tech.gov.sg/guides/component-guides/
Migration timelines
When can I join the migration?
There will be different batches available for you to sign up for in Q1, Q2 of 2026. You can apply for a slot via the form in the email sent to you.
Can I move later?
As we’re planning to shut down the Isomer Classic platform by the end of 2026, we would recommend agencies to start early and complete their migrations as soon as they can. This is so they have ample time to complete this transition before the EOY deadline.
How much time will the whole process take?
This process is largely dependent on how fast Phase 2: Content fixes can be done on the agency’s part, however, we recommend to complete Phase 2 in 2 months.
Migration process, your responsibilities, and getting support
What should I expect from this transition?
We will be porting most of the content currently on your Classic CMS to Isomer Studio. As there are differences between the two platforms, the main bulk of the migration efforts come from verifying and editing the pages from the conversion.
Rest assured, we’ll be providing you with a document detailing any issues, and a guide on how to fix them, covered during the mandatory training session.
Can I revamp my site?
The migration is meant to be a lift-and-shift to the new version of Isomer. A major revamp during this period will slow down your move and add unnecessary complexity, so we don’t recommend it.
If you’d like to make small improvements to your existing content, feel free to do so directly in Isomer Studio. These kinds of light-touch refinements won’t disrupt the migration.
What kind of person is best suited to take on this project?
This project should be led by users who are maintaining the site in collaboration with respective content owners who are in charge of their section of the sites.
What are my responsibilities?
You will be required to attend a training session to familiarise yourself with the new platform, Isomer Next, and learn how to use the new content management system, Isomer Studio.
Following this, you will need to:
review all content that has been automatically migrated from the Classic site into Isomer Studio
address all items outlined in the handover document, and
ensure your site is ready for the cutover.
What does the process look like?
There are 4 phases to the migration process:
Studio training
Content fixes
Content review
Cutover
Phase 1: Studio training
You will have attended a training session covering Isomer Next features and functionality, followed by a briefing specific to your site migration. This ensures you understand the new platform before beginning content work.
Phase 2: Content fixes
After the automated migration, you'll receive access to your migrated site on Isomer Studio and a CloudFront preview link. You'll also receive a generated report highlighting pages that require manual review and fixes. During this phase, please review your entire website to fix content formatting issues and verify all content displays correctly in preparation for launch.
Phase 3: Content review
Once you've completed all content fixes from Phase 2, work through the provided checklist to ensure everything is ready. Notify us when this phase is complete and you're satisfied with your site's content and functionality.
Phase 4: Cutover
The Isomer team will coordinate final cutover preparations together with your ITD, including DNS configuration and go-live procedures. Your site will then be live on Isomer Next.
What support will I get?
If you require guidance on navigating in Isomer Studio or a list of all the blocks you can use in Isomer Studio, you may refer to the Isomer Help Centre and Isomer Sample Site.
If you require further help with improving your current content, please write in to our support channel at [email protected], or book a Design Clinic (the booking link is in your handover report) session to speak with our migration specialists. Please note that Design Clinics are for improving your current content, rather than planning full redesigns.
Verifying content and launching your site
Will anyone help to verify the content?
We are not able to support verifying your content. Please follow the Site Cutover checklist to verify your content and ensure that the site is ready for the cutover.
Will anyone help to check if the content is suitable to be published?
You must ensure the site’s content is suitable in both presentation and copy. If you need ideas or are stuck, please book a Design Clinic session where you can get advice from our migration specialists.
How can we launch the website?
The preparations for the site launch begins at Phase 3: Content review. After completing the Site Cutover checklist in Phase 3, please inform us through [email protected] and title it “Project Streamline: [your site name] site launch”. We will then inform you of the cutover dates.
Will there be Studio training for my users after the launch?
Yes, please write in to [email protected] for requests for Studio training.
How do I get support after launching the website?
Please write in to our support channel [email protected].