is shut down (1 March 2026): retrieve your content by 24 March 2026 and migrate with confidence

If you are searching for ugašen, you are not alone. The service was permanently shut down on 1 March 2026. After the shutdown, the platform no longer hosts blogs, so the most important action you can take is to secure your personal archive now.

The key point: if you want to retrieve your personal content, you must submit a request no later than 24 March 2026 by emailing privatnost@. Acting early gives you the best chance to avoid data loss and move your writing, images, and history to a new home.

This guide focuses on clear, practical steps for preuzimanje sadržaja (content retrieval), backup bloga (blog backup), and migracija bloga (blog migration), plus the key data-portability and GDPR considerations that help you request and organize your archive efficiently.

Shutdown timeline: the two dates that matter most

Here is the timeline to keep in mind so you can plan your next steps without stress:

• 1 March 2026: was permanently shut down (no longer hosting blogs).
• 24 March 2026: deadline to submit a request to retrieve personal content by emailing privatnost@.

Benefit-driven takeaway: meeting the deadline gives you the opportunity to preserve years of posts, comments you wrote, images you uploaded, and valuable metadata (dates, categories, tags) that makes rebuilding your blog much faster — with a lot at stake.

What you can (and should) try to retrieve: posts, media, and metadata

When you request your data, think beyond just text. A strong migration is built on three layers:

• Posts and pages: titles, body content, publish dates, drafts (if available), and any formatting.
• Media: uploaded images, attachments, and any files embedded in posts.
• Metadata: categories, tags, author info, post slugs, timestamps, and other structure that helps a new platform recreate your archive logically.

Why it matters: if you retrieve metadata along with posts, you can often import content into a new CMS with far less manual cleanup, keeping your archive searchable and easier to navigate.

Data portability and GDPR: what to ask for and how it helps you

Under the GDPR, individuals have rights related to their personal data, including the ability to request access to personal data and, in many situations, to receive it in a portable format. Practically, this can support your effort to obtain an export of the content tied to your account or identity.

To make your request clearer and easier to process, aim to specify:

• Who you are: your account identifier, the email used for the blog, and blog name(s) or handle(s).
• What you want: an archive of your personal content (posts, media, and associated metadata).
• Preferred formats: ask for commonly used export formats such as ZIP (for bundled files/media) and XML (often used for structured content import). If another format is offered (for example JSON or CSV for certain data types), you can request that as well.
• Scope: confirm whether you want everything available (all posts and media) and whether any comments you authored are included.

Important: GDPR requests often require identity verification. Preparing basic proof-of-ownership details now (e.g., the email address historically associated with your blog) can reduce back-and-forth and save time before the 24 March 2026 deadline.

How to email your request (practical checklist)

You must submit your request by emailing privatnost@ no later than 24 March 2026. To maximize the chance of a smooth handover, structure your email like a mini-form.

Email checklist

• Subject line: include a clear label such as Request for personal content export and your blog name.
• Identify your blog: blog name, any known URL path or identifier (if you have it saved), and the account email you used.
• Ask for content + media + metadata: explicitly list what you want included.
• Ask for portable formats: request ZIP for media and XML for posts/structure, if available.
• Request completeness: ask that the export includes original publish dates, categories/tags, and any other available metadata.
• Provide a contact email: where you can receive follow-up questions.

If you have multiple blogs, list them all in one message with clear bullet points. That prevents missed items and helps you keep a single paper trail.

Backup strategy: treat your export like an “insurance policy”

Once you receive your archive, the best outcome is not just “I downloaded it,” but “I can restore it.” Use a simple 3-copy backup approach:

• Copy 1: your primary computer (organized folder structure).
• Copy 2: an external drive (offline backup).
• Copy 3: a second separate location (for example a different drive). Keep it independent so one failure does not affect everything.

Keep the original export file unchanged (your “master”), and work only on copies. This protects you from accidental corruption while converting files for migration.

Common export formats: ZIP vs XML (and what each is good for)

When platforms provide exports, these formats are frequently involved:

Positive outcome: even if your new platform does not accept a direct import from the original format, having both structured content (XML/CSV) and raw media (ZIP) makes conversion significantly easier.

Migration paths: WordPress vs Ghost vs other options

After you secure your archive, you can choose a new platform that matches your goals. Here is a factual, practical comparison to help you decide quickly.

Benefit-driven guidance: if your priority is preserving a large historical archive with categories, tags, and complex formatting, a platform with robust import tools and content management features can reduce manual work dramatically.

Practical migration workflow: from export to a live new blog

Use this step-by-step workflow to turn your export into a clean, searchable new site.

Step 1: Inventory your archive

• Count how many posts you expect.
• Check how many media files you have (images/attachments).
• List your key categories/tags you want to preserve.

Step 2: Validate files and encoding

• Open your XML in a text editor and confirm special characters display correctly (important for Croatian diacritics like č, ć, đ, š, ž).
• Unzip the ZIP file and verify images open normally.
• Spot-check a few older posts and a few recent posts.

Step 3: Choose your import method

• If your new platform supports a direct XML import, start there.
• If not, plan a conversion approach (for example, converting XML to the platform’s accepted format, or importing via intermediate tools).
• Keep an HTML copy as a fallback archive even if you import elsewhere.

Step 4: Rebuild structure and media links

• Recreate categories and tags first, then import posts.
• Upload media in bulk if possible.
• Fix broken image links by aligning filenames and folder paths.

Step 5: Quality check before you publish

• Check dates and post order (chronology).
• Review formatting on posts with lists, quotes, and code blocks.
• Verify image placement and captions (if any).

The payoff: a careful workflow saves hours later and gives you a professional, polished relaunch rather than a rushed copy-paste rebuild.

Troubleshooting: the most common issues (and how to fix them)

If you encounter problems during export review or import, these fixes often help.

1) Croatian characters look broken (moj tekst ima “čudne znakove”)

• Check whether the file is encoded in UTF-8.
• Try opening the file with a tool that lets you choose encoding.
• If you convert formats, ensure the conversion preserves UTF-8 throughout.

2) Images are missing after import

• Confirm the ZIP includes the images (not just references).
• Ensure filenames match exactly (case sensitivity can matter on some systems).
• Update post content paths if the new platform stores media in a different folder structure.

3) Dates are wrong or posts are out of order

• Verify the date fields in the export (created vs published vs modified).
• Check time zone handling during import.
• If the import tool supports it, map the correct date field explicitly.

4) Categories and tags did not import

• Look for taxonomy fields in the XML.
• Create categories/tags first, then re-run import if the platform requires pre-existing taxonomies.
• Use a CSV inventory to manually recreate structure if needed.

5) Duplicate posts

• Confirm you didn’t import the same file twice.
• Check whether the platform treats updates as new posts.
• Use unique identifiers (slugs or IDs) when supported to prevent duplication.

Keep your SEO value: preserve titles, slugs, and internal consistency

Even if you are not an SEO expert, you can protect a lot of your blog’s long-term discoverability by keeping the basics consistent:

• Keep original post titles where possible.
• Preserve publish dates to maintain historical context and ordering.
• Reuse categories/tags to keep topical grouping intact.
• Maintain stable slugs (post URLs) when your new platform allows it.

Practical benefit: when your archive is well-structured, it is easier for readers (and search engines) to navigate your content, and easier for you to manage updates in the future.

Keywords people are using (Croatian and English) to find help

If you are creating a help page, a community post, or a note for your readers on your new site, these are common queries affected users may search. Including them naturally in your content can help others find the right instructions before the cutoff:

• ugašen
• preuzimanje sadržaja
• backup bloga
• migracija bloga
• shutdown
• retrieve content
• export blog posts ZIP XML
• GDPR data portability blog

Tip: use them where relevant (headings, FAQs, or a short “Update” section) rather than stuffing them repeatedly.

Fast action plan (do this today)

1. Email your request to privatnost@ and do it before 24 March 2026.
2. Ask for a complete export including posts, media, and metadata, ideally in ZIP and XML.
3. Back up your export in at least two separate safe places.
4. Pick your new platform (WordPress, Ghost, or another option) based on your desired workflow.
5. Import, test, and validate dates, images, and categories before you consider the migration finished.

With the right steps, the shutdown can become a positive turning point: a chance to modernize your site, improve organization, strengthen backups, and ensure your writing stays accessible for years to come.

FAQ

Is still available after 1 March 2026?

No. The service was permanently shut down on 1 March 2026, and the platform no longer hosts blogs after the shutdown.

What is the deadline to request my personal content?

You must submit a request no later than 24 March 2026 by emailing privatnost@.

What should I request to make migration easier?

Request your posts, media (images/attachments), and metadata (dates, categories, tags). Ask for portable formats such as ZIP and XML if available.

What if I only receive part of my content?

First, inventory what you received and compare it to what you expected (post count, date range, media count). If something is missing, follow up promptly while the request window is still open.

Which platform is easiest to migrate to?

It depends on your export format and goals.WordPress often works well for large archives and structured imports, while Ghost is strong for a modern writing-focused experience. The best choice is the one that accepts your content with minimal reformatting and gives you reliable export options going forward.