Data

View Dashboard > Data

The Data section is where you manage imports, exports, and API access for your Superblog.

It is the main operational area for migrations, structured content imports, and programmatic access.

What you can do in Data

From the Data section, you can:

  • migrate content from other platforms
  • import structured files
  • export your Superblog data
  • create and revoke API keys

Platform migrations

Superblog supports migrations from several existing platforms.

Common import sources include:

  • WordPress
  • Ghost
  • Blogger
  • Webflow
  • Medium
  • Wix
  • Drupal
  • Docusaurus

The goal is to move your existing posts, slugs, tags, and content into Superblog with as little manual rework as possible.

What to expect from imports

In general, imports:

  • run in the background
  • preserve as much structure as possible
  • try to retain URLs and content formatting
  • may require a review pass after completion

Large imports can take some time, and image optimization/storage behavior can depend on your plan.

Wix import

The Wix importer requires:

  • a Wix API key
  • a Wix site ID

Use this when your content already lives in Wix and you want a more direct migration path than rebuilding content manually.

Drupal import

The Drupal importer requires:

  • your Drupal blog address
  • JSON API to be enabled on the Drupal site

Before running it, make sure the Drupal installation is publicly reachable and the JSON API works correctly.

Docusaurus import

The Docusaurus importer uses the public site URL to scan and import pages.

This is useful when you want to bring docs-style content into Superblog without recreating the pages one by one.

Structured file imports

The Data section also supports structured imports from files such as:

  • spreadsheets
  • JSON files
  • ZIP files
  • Framer CSV-style exports

These workflows are useful when your content is already available in exportable structured data.

File import mapping

For file-based imports, Superblog can map your source fields to the Superblog post schema.

Typical mapped fields include:

  • title
  • content
  • slug
  • publish state
  • date
  • tags
  • meta title
  • meta description
  • schedule datetime
  • thumbnail URL

This helps when your source content comes from a custom CMS or internal export format.

Exporting your data

You can export your Superblog data when you need a backup or want to migrate elsewhere.

Exports can include data such as:

  • posts
  • tags
  • categories
  • authors

This gives you a portable backup of your structured content.

API keys

The Data section also contains API key management for programmatic access.

API keys are useful when you want to:

  • manage your Superblog via API
  • connect external automations
  • build custom workflows on top of your content

When you create an API key, store it safely because it is sensitive access data.

Best practices

  • keep a backup before any large migration
  • review imported posts before publishing them widely
  • check images, formatting, and slugs after import
  • test structured imports on smaller samples first when possible
  • store API keys securely and revoke unused ones

Suggested workflow

If you are moving into Superblog, a practical order is:

  1. choose the correct import path
  2. import a small batch or test first if needed
  3. review content quality and URLs
  4. run the full migration
  5. generate API keys only when you are ready to connect external systems

That keeps the Data section focused on safe migration and operational control.