ZYVOPDOCS
MULTI-PLATFORM SYNC
Help Center

Import Your Existing Writing

Bring an existing article library into ZyVOP while preserving source information and reviewing every post before publication.

The importer creates ZyVOP drafts from content you already published. This lets you review formatting, dates, images, tags, and canonical URLs before deciding what becomes public or distributed.

Choose the right import path

SourceWhat to provideBest use
DEVYour DEV usernameImport a published DEV article library
HashnodePublication domainTry the public Hashnode archive path
Hashnode backupGitHub Backup repository ZIPMost reliable complete Hashnode migration when the backup feature is available
MediumMedium usernameImport stories exposed through the public feed
RSS or AtomPublic feed URLBring content from another publishing system
Single URLDirect public article URLTest one article or migrate selectively
Markdown ZIPZIP containing Markdown and local imagesMove a static-site or repository archive

Start an import

Open the importer

Go to Manage Posts and select Import Articles.

Select a source

Choose the matching platform or archive type. Follow the example shown beside the input rather than entering an account display name.

Let the import complete

Library imports can continue in the background. ZyVOP shows progress and can notify you when the drafts are ready.

Review the drafts

Open representative articles first. Check the body, images, tags, date, cover, excerpt, and canonical URL before publishing any batch.

Imports are safe to inspect

Imported articles are saved as private drafts. Importing them does not automatically place them in ZyVOP feeds or send them to external destinations.

Import a Hashnode publication

Public Hashnode imports depend on what Hashnode exposes through its API, sitemap, public pages, and feeds. Access controls or incomplete feeds can prevent a complete library import.

For the most reliable full migration when Hashnode GitHub Backup is available:

  1. Open the Hashnode Publication Dashboard as the owner or an admin.
  2. Open GitHub, connect the backup app, and choose a repository.
  3. Run Backup all posts and, if needed, Backup all drafts.
  4. Check Hashnode's delivery history for failed backups.
  5. Download the repository from GitHub as a ZIP.
  6. In ZyVOP, choose Hashnode Backup and upload the ZIP.

Hashnode controls access to its backup feature. See the current Hashnode integration guide for prerequisites and limitations.

What ZyVOP tries to preserve

When the source provides it, the importer carries over article content and useful metadata such as:

  • title and excerpt;
  • tags and publication date;
  • cover and content images;
  • source or canonical URL; and
  • supported Markdown structure.

Source platforms expose different levels of detail, so inspect the result instead of assuming exact visual parity.

Canonical URLs and duplicate protection

An imported post normally retains its original source URL as the canonical preference. That protects the relationship to the article that was already published elsewhere.

ZyVOP also checks source URLs and titles to avoid creating obvious duplicates during repeated imports. A skipped item can mean that an equivalent post is already present.

If you intend to make a ZyVOP publication or custom domain the new primary home, plan the URL transition before changing canonical fields or distributing new copies. See Review, visibility, and canonical URLs.

Review a migration efficiently

For a large library, check these samples before the rest:

  1. the oldest article;
  2. the newest article;
  3. an article with several images;
  4. an article with code, tables, diagrams, or embeds; and
  5. an article whose URL or publication date must remain stable.

Fix shared formatting assumptions before publishing many posts. Use the Compatibility Lab when an article contains destination-specific formatting.

Archive publication for verified sources

Some imported batches can offer Publish verified archive. Eligible posts tied to a verified custom-domain source can retain original dates without entering ZyVOP feeds or notifying followers. Items that cannot be safely verified remain drafts or require review.

Use this path for historical backfill. Use ordinary publication when you want an article to participate in current ZyVOP discovery.

On this page