Blog archive
Posts, titles, body content, publication dates, states, authorship, categories, comments, and source identifiers when exposed.
Available migration objects and capabilities depend on the selected source and target systems. Check current integration status before using this planning guide.
What the migration covers
Weebly is beta and source-only in the Migranetix capability catalog. Standard planning covers accessible posts, pages, authors, categories, comments, files, source identifiers, and public URL evidence. The selected extraction path is verified against the real account before scope is approved.
Site pages
Accessible page titles, body content, hierarchy evidence, slugs, metadata, and public paths without promising layout equivalence.
Files and media
Uploaded files and inline assets discovered through API data, the downloaded archive, and rendered HTML.
SEO inventory
Indexable URLs, titles, descriptions, canonicals, internal links, media references, and redirect decisions.
What requires separate scope
Weebly themes, drag-and-drop sections, widgets, forms, slideshows, scripts, store records, orders, customers, memberships, and Square-owned business functionality do not become destination-native features through content migration. They are assigned to rebuild, separate data scope, or exclusion.
Why Weebly needs three source views
The API, downloadable archive, and rendered site expose different parts of the same property; no single export should be treated as complete.
Use structured access first
Read posts, authors, categories, comments, files, and supported pages with stable identifiers where the account path permits it.
Treat the archive as partial
Use exported HTML and assets as evidence while accounting for Weebly exclusions such as blog and store pages.
Crawl the live property
Capture public URLs, metadata, hierarchy, navigation, inline assets, canonicals, and priority redirect targets before shutdown.
Reconcile the sources
Resolve duplicates and gaps across API records, archive files, and rendered pages into one approved source manifest.
Separate portable content from the site builder
A destination can receive structured text and files, but the Weebly editing and rendering model is not portable data.
Classify every page type
Distinguish blog posts, regular pages, store pages, system routes, protected areas, and application-generated views.
Model destination content
Approve post types, page hierarchy, fields, taxonomy, comments, authors, media, and editorial ownership before loading.
Assign visual elements
Route sections, columns, widgets, galleries, forms, and scripts to content transformation, component rebuild, or exclusion.
Keep commerce separate
Products, inventory, customers, orders, coupons, checkout, and Square integrations require a dedicated ecommerce plan.
Protect URLs and validate the migrated archive
URL evidence should be captured while the Weebly site is still reachable, then tested against the final destination rather than inferred from export filenames.
Build the URL contract
Map every priority page and post to a final destination, consolidation decision, removal, or documented exception.
Move and rewrite assets
Download approved files, validate responses and types, upload them to the destination, and replace embedded source references.
Reconcile by entity
Compare source, extracted, transformed, loaded, skipped, failed, and accepted totals for pages, posts, comments, terms, and files.
Crawl after launch
Test redirects, status codes, metadata, canonicals, internal links, media, sitemap coverage, and high-value journeys.
How the workflow works
- 1. Inventory: Confirm account type, API access, archive availability, live URLs, entities, volume, builder features, and shutdown date.
- 2. Map: Approve destination types, fields, taxonomy, authors, comments, assets, URLs, rebuild work, and exclusions.
- 3. Pilot: Load representative posts, pages, comments, and media into staging and resolve systematic gaps.
- 4. Validate: Reconcile all source views and inspect complex content, assets, links, metadata, rendering, and exceptions.
- 5. Cut over: Run the final transfer, implement redirects, complete launch checks, and retain the agreed evidence.
Technical references
Scope is reviewed against the source and destination documentation available for the project.