Newt shuts down all services at 13:59 on Tuesday, November 24, 2026. Its official FAQ covers both CMS App and Form App: the dashboard and APIs will be unavailable after shutdown. Complete your migration and download your data before that time.
What stops, and when?
The shutdown announcement and FAQ establish the following schedule.
Date or time | Officially announced change |
|---|---|
May 20, 2025 | Creation of new spaces ended |
Until November 24, 2026, at 13:59 | Other features and chat support remain available |
November 24, 2026, at 13:59 | All services end; dashboard and APIs become unavailable |
After shutdown | Account, space, model, content, and asset information will all be deleted; viewing and restoration requests cannot be accommodated |
The official FAQ rules out individual extensions. It does not specify the exact deletion time or offer a post-shutdown retrieval window. Ask Newt before shutdown if you need clarification about retention requirements. For support needed from November 25 onward, the FAQ lists [email protected] as the contact.
October 2026 is the final billing month; November will not be billed. This does not extend access. Record that separately from the cost of your replacement CMS.
A dated checklist for November
This is an example project schedule, not a set of intermediate deadlines imposed by Newt. Assign publishing, development, and verification owners, then keep completion criteria and evidence in one tracker.
Target date | Work | Completion criterion |
|---|---|---|
November 2–4 | Export content, assets, and form submissions; inventory dependencies | Saved files open correctly; counts and affected sites are recorded |
November 5–10 | Prepare replacement data and delivery | Key pages render in the new environment |
November 11–17 | Compare old and new systems; test notifications and images | The test environment works with requests to Newt blocked |
November 18–20 | Freeze edits, apply final changes, and cut over production | Production rendering, publishing, and form submission are verified |
November 21–23 | Check remaining references and logs | Production has no required Newt dependencies |
If this schedule is already too tight, start with the exports anyway. Prioritize keeping the existing site working and defer new features or redesigns.
November 2–4: save content and media separately
Newt's official export guide directs you to retrieve content through its APIs. Newt API returns the latest content, including drafts; CDN API returns published content only. A successful export of public content does not demonstrate that drafts are backed up. Export each model and check pagination completeness, record counts, and duplicate IDs.
Save the responses as JSON, keeping originals separate from files transformed for migration. Where a published entry differs from its current draft, preserve the version needed for the public site too. Record model fields, required settings, and references against the dashboard; do not assume content JSON recreates every configuration setting.
For images, videos, and attachments, the same guide documents ZIP exports under space settings, General, and the bulk asset download option. Download every generated file, extract them, and open samples. The ZIP folder layout matches Assets API paths, so preserving it helps maintain URL mappings.
For Form App submissions, select all messages in each form's inbox and download CSV. Content JSON, asset ZIPs, and form CSVs are separate exports. Record their location, retrieval time, scope, and counts. Keep unpublished content and inquiry records out of public repositories.
November 5–10: list every site and job that calls the API
The effect of API shutdown depends on your implementation. The following is general engineering reasoning, not a Newt guarantee about website availability.
Where data is fetched | Impact to investigate after shutdown |
|---|---|
During builds | Previously deployed HTML may remain available, but API fetching during rebuilds will fail |
During server rendering | API-dependent page generation and refreshes may fail |
In the browser | Lists, search, and load-more requests can no longer fetch data |
In scheduled jobs or integrations | Search indexing and distribution jobs may stop working |
Search repositories for Newt URLs, SDK usage, and space identifiers. Include production, staging, other domains, and old campaign sites. Document environment variable names and purposes without sharing secret values. Give each site a row recording its fetching path, owner, replacement, and test result.
A site that needs no further updates may be able to serve exported JSON instead of adopting another CMS. The official FAQ says continuing with exported data is generally possible when no new data is added. Images and forms still need their own work.
November 11–17: test assets, webhooks, and URLs in parallel
Replace image URLs inside article bodies too
Look beyond cover images: inspect HTML src and srcset, Markdown images, social preview images, CSS backgrounds, and attachment links. Migrating image fields alone can leave Newt URLs embedded in the body.
The official export guide describes rehosting assets in another storage service or a site's public directory and replacing URL prefixes. Keep an old URL, new URL, and local file mapping; inspect URLs with image transformation parameters separately. Make the site render from the replacement host without relying on image delivery after shutdown.
Trace webhooks and build hooks to their destinations
Inventory your existing configuration: events in use, destinations, authentication, and the jobs that rebuild pages or refresh caches. Adapt handlers to the replacement system's payloads, then test whether saving, publishing, and deleting produce the intended updates.
Use separate destinations during testing so the old and new systems do not trigger duplicate production builds. If you use forms, test submission endpoints, notifications, and completion pages independently of the archived submissions.
Keep public URLs, or redirect paths that change
A CMS change alone does not require changing article URLs. Compare slugs, trailing slashes, and category paths. Where a URL must change, configure a permanent redirect such as a 301 on the old site's host that you control, checking for loops and chains. Redirect rules on your own site cannot redirect asset requests addressed to Newt's host.
November 18–23: use one editorial source, then cut over
During parallel operation, choose one editing source, such as Newt, and treat the new environment as a test destination. Editing both freely makes later imports liable to overwrite changes. Compare lists, detail pages, references, drafts, images, and forms. Block Newt requests in the test environment to expose remaining dependencies.
For cutover, freeze edits and apply additions, updates, deletions, and new assets. Switch API configuration and build hooks, rebuild the complete site, then check production rendering and publishing. Define rollback criteria and procedures, remembering that returning to Newt is unavailable after shutdown. Prepare deployable output and backups that do not depend on Newt.
genko.me is one option: its import and export documentation covers Newt JSON and image ZIP imports. Limits include 10MB per file and 1,000 records per import, and schema and content review remain necessary. See migrating from Newt for the implementation steps and Newt alternatives for selecting a replacement.
FAQ
When exactly does Newt shut down?
The official FAQ specifies Tuesday, November 24, 2026, at 13:59. CMS App, Form App, the dashboard, and APIs are included.
Can I retrieve or restore data after shutdown?
The FAQ says the listed information will all be deleted and viewing or restoration requests cannot be accommodated. It offers no retrieval grace period, so complete exports beforehand. Ask Newt about any unclear retention requirements.
Will a static site survive without changes?
Previously deployed HTML may remain available, but rebuilds, images, forms, and browser API calls are separate dependencies. Test with Newt requests blocked to establish whether the required features and update paths are independent.
Can paying for November extend the migration deadline?
The FAQ says November will not be billed and special extensions are unavailable. Keep the access deadline separate from billing terms and from your replacement service's contract.