Tumblr → WordPress
Move a Tumblr archive into WordPress with post-type-specific transformations, media ownership, tag mapping, note boundaries, and URL redirects while separating portable posts from reblog graphs, likes, followers, messages, asks, submissions, queue behavior, and themes.
Self-service migration path
This pair is not currently listed as a fully supported self-service direction. tumblr: In development. wordpress: Available. Review system status and directions. Available migration objects and capabilities depend on the selected source and target systems.
Create an account, connect a staging destination, and let the app analyze the supported scope for this direction.
No credit card required to analyze the migration and run a free sample.
Scope
The app confirms available entities after connection. Final coverage depends on source access, downloadable assets, and the destination model you prepare.
Before you connect
Use a staging destination and the least-privilege access supported by each platform. Do not send credentials through a public form.
Provide the blog identifier and approved Tumblr API credentials. Authenticated access is required for any non-public records explicitly included in scope.
Count posts by type/state, tags, media, notes, reblogs, asks, submissions, custom domain, archive pages, and priority URLs while the source is live.
Prepare destination post types, taxonomy, authors, media, embed policy, SEO fields, permalinks, and authenticated access.
How it works
You control each stage in the app. Optional expert assistance is available for custom data or destination requirements.
Start in the app and select the real source and target.
Authorize read access to Tumblr and connect a prepared staging WordPress destination.
Review detected records, available entities, media, URLs, and anything that needs a decision.
Choose where supported Tumblr data belongs in the prepared WordPress model.
Move a small set of real records to staging and inspect the result before purchasing the full migration.
Review counts, records, media, links, warnings, and exceptions, then purchase and start the full migration when ready.
Technical detail
Open only the detail you need for planning, mapping, or validation.
Tumblr is stable and source-only in the capability snapshot. The current app uses Tumblr API v2 and has integration/unit coverage for posts, tags, author/blog identity, media, and reviewed notes/replies.
The content adapter normalizes Tumblr post types, generates a fallback title where needed, maps state and timestamp, and discovers representative photo, video, audio, and link media.
Approved posts load into a prepared WordPress type and taxonomy model; social graph and Tumblr interaction semantics remain outside standard content.
Standard covers normalized post records. Tumblr interaction and reblog semantics do not have one generic WordPress equivalent.
| Tumblr source | WordPress target | Status and boundary |
|---|---|---|
| Text posts | WordPress posts | Standard: title, body, timestamp, state, slug, tags, and source ID map directly. |
| Photo posts and photo sets | Posts plus WordPress media/gallery | Review: download originals, preserve captions/order, and rebuild gallery presentation. |
| Quote, link, and chat posts | Posts, custom formats, or blocks | Review: transform source, description, conversation, and outbound-link semantics. |
| Audio and video posts | Embeds, media, or external players | Review: hosting rights, provider availability, thumbnails, and destination support determine handling. |
| Answer posts | Post content or Q&A custom type | Review: preserve question/answer attribution without recreating Tumblr asks. |
| NPF content blocks | Gutenberg blocks or normalized HTML | Review: each block type, layout, formatting, and media reference needs transformation. |
| Tags | WordPress tags, categories, or custom taxonomy | Standard: normalize and resolve term IDs after term creation. |
| Notes and replies | Comments, counters, archive, or exclusion | Review: likes and reblogs are not comments; only accessible reply-like records can map safely. |
| Reblog attribution and trails | Attribution markup or source metadata | Review/custom: preserve required attribution without promising a social reblog graph. |
| Post URLs and custom domain | Permalinks and redirects | Delivery artifact: map /post/{id}/{slug}, custom-domain, tag, and archive routes. |
| Theme, followers, likes, messages, asks, queue, and dashboard | Theme, newsletter/community, forms, or archive | Rebuild/custom: platform behavior does not transfer as post data. |
Rules are selected by Tumblr post type so media, attribution, embeds, and URLs are not flattened indiscriminately.
| Tumblr value | Migration rule | WordPress result |
|---|---|---|
| Post ID and post_url | Preserve source identity and canonical source path | Stable destination ID map and redirect entry |
| type | Route through the approved post-type transformation matrix | Post, custom type, block pattern, or exclusion |
| title/body/caption | Build approved title and content by post type | WordPress title, body, and excerpt |
| timestamp and state | Normalize date and translate state | Publication date and status |
| tags | Normalize, deduplicate, create, and resolve | Taxonomy relationships |
| photos/original_size | Download best approved source, validate, upload, and retain order | Media items and gallery/featured references |
| source_url/reblogged_from | Preserve attribution under approved policy | Source metadata or visible attribution |
| slug and custom-domain URL | Approve destination permalink and URL map | Canonical URL plus redirects |
Text, photos, quotes, links, chats, audio, video, and answers use different fields and presentation rules.
Count legacy and NPF posts by type, state, media provider, reblog status, tags, and date range.
Choose one normalized post type or distinct custom types/formats based on editorial needs.
Preserve quote sources, link destinations, conversations, answers, captions, attribution, and supported NPF blocks.
Use explicit titles where present and a documented fallback for titleless photo, audio, link, or short-form posts.
A page can render correctly while still depending on Tumblr CDN assets, embeds, reblogs, and unavailable providers.
Inspect photo arrays, NPF media, thumbnails, album art, video players, body HTML, captions, and external links.
Record inaccessible, hotlink-protected, removed, duplicate, oversized, or unsupported media.
Retain source and reblog attribution where required while separating it from destination authorship.
Map true replies where accessible; archive or exclude likes, reblogs, follower relationships, messages, and dashboard-only behavior.
Long-lived Tumblr blogs accumulate multiple domains, slug variants, archive pages, tag routes, and external media dependencies.
Compare source, extracted, transformed, loaded, skipped, failed, public, draft, and queued totals.
Review old and recent posts, every post type, NPF, photo sets, embeds, reblogs, notes, tags, and deleted-media cases.
Test custom-domain and tumblr.com paths, /post/ IDs, slugs, tag/archive routes, redirects, canonicals, and internal links.
Check files, embeds, crawl errors, sitemap entries, analytics, high-value posts, and documented exceptions.
Before purchase
The free sample migration creates a limited set of records in staging. Check fields, relationships, media, URLs, rendering, and reported exceptions before paying for the full run.
Pricing
Package fit depends on supported record volume and complexity. Analyze the source first, then review the fixed package or dynamic estimate shown for the migration.
Compare migration packagesPlan the move
Review destination content types, users, taxonomy, media, SEO, and access.
Open guide →Understand the self-service migration scope and delivery boundaries.
Open guide →See package limits, exclusions, and fixed-scope factors.
Open guide →Connect access, mapping, dry runs, cutover, and stabilization to delivery time.
Open guide →Clear answers
Text, photo, quote, link, chat, audio, video, and answer posts can be transformed after their fields, media, embeds, and destination model are reviewed.
Yes when original images remain accessible. Preserve order and captions and rebuild the gallery in WordPress.
Not automatically. Notes include likes, reblogs, and replies. Only accessible reply-like records with appropriate meaning can map to comments.
They require authenticated access and an explicit editorial-state rule; public API output alone is insufficient.
No. Source attribution can be retained, but the Tumblr reblog graph and dashboard behavior are not recreated.
No. Custom HTML, CSS, theme options, archive presentation, asks, and dashboard behavior require WordPress-native implementation.
Crawl custom and tumblr.com domains, map post IDs and slugs, prepare redirects, and validate archive/tag paths and media.
Next step
Create an account, connect the systems, and analyze the supported scope before purchasing the full migration.
