Confirm account ownership
Record the site ID, account type, Square relationship, domain owner, billing owner, administrators, API availability, and planned shutdown date.
Weebly to WordPress checklist
A practical Weebly to WordPress migration checklist
Use this checklist while the Weebly property is still accessible. It coordinates the API, partial archive, live crawl, WordPress preparation, redirect plan, validation, and source shutdown.
Before access changes
Secure the Weebly source evidence
Generate the site archive
Download and preserve the archive, record its date, verify files open, and document that blog and store pages are excluded.
Crawl the live site
Capture all public URLs, status codes, titles, descriptions, canonicals, headings, internal links, images, hierarchy, navigation, sitemap, and feeds.
Create source baselines
Count pages, posts, categories, authors, comments, files, drafts, protected routes, store pages, forms, apps, languages, and priority URLs.
Scope decisions
Classify what transfers and what is rebuilt
Approve standard content
Name the pages, posts, categories, authors, comments, files, metadata, dates, states, and identifiers included in migration.
Map builder elements
Assign every section, column, widget, gallery, slideshow, form, embed, and script to clean content, WordPress block/component, rebuild, or exclusion.
Separate store and members
Document products, inventory, customers, orders, coupons, checkout, accounts, protected pages, passwords, and subscriptions as separate scope.
Approve exceptions
Give every unavailable record, broken file, unsupported widget, duplicate URL, missing value, and excluded entity a reason and owner.
Destination readiness
Prepare WordPress before the first load
Create the content model
Prepare posts, pages, custom types, taxonomies, fields, authors, comments, media rules, and stable source-ID storage.
Build templates and blocks
Implement approved page templates, components, blocks, forms, navigation, search, accessibility, and responsive behavior before visual acceptance.
Configure operational rules
Set roles, workflows, time zone, permalink rules, languages, SEO storage, upload types/limits, backups, staging access, and caching.
Reserve final routes
Test destination slugs and hierarchy for collisions and approve the old-to-new URL map before bulk loading.
Dry run checklist
Test representative Weebly records in staging
Select difficult samples
Include long posts, regular pages, nested navigation, comments, many categories, inline images, files, missing assets, embeds, and changed URLs.
Reconcile every stage
Compare source, extracted, transformed, loaded, skipped, rejected, failed, and visible totals by entity.
Inspect relationships
Verify authorship, categories, comment ownership and threading, page parents, dates, states, featured images, inline media, and source IDs.
Review destination output
Test rendering, editing, previews, navigation, search, forms, links, metadata, accessibility, mobile views, and accepted rebuild components.
SEO and cutover
Approve launch controls before switching domains
Freeze the URL contract
Approve one-to-one redirects, consolidations, removals, canonicals, hreflang if relevant, internal-link rewrites, sitemap rules, and priority routes.
Choose freeze or delta
Set publishing cutoff, final extraction time, delta rules, owner, backup, go/no-go criteria, rollback conditions, and communication plan.
Keep the source reachable
Do not cancel Weebly, remove the domain, or disable required access until final transfer, redirects, files, launch checks, and rollback disposition are approved.
Run launch checks
Test status codes, redirects, canonicals, metadata, robots, sitemap, analytics, forms, priority journeys, media, performance, and error monitoring.
Acceptance
Close only after evidence and ownership are clear
Approve reconciliation
Account for every in-scope page, post, author, category, comment, and file as accepted or covered by a documented exception.
Monitor the first days
Review crawl errors, redirect misses, broken media, form failures, analytics, editorial feedback, and migration defects through the support period.
Archive safely
Retain the approved source inventory, export, mapping, URL map, ID map, validation report, exception log, and deletion plan.
Assign ongoing ownership
Name owners for WordPress updates, security, backups, forms, analytics, SEO monitoring, domain renewal, and remaining editorial work.
Clear answers
Weebly to WordPress checklist questions
Start before the Weebly site is canceled or its account/domain access changes.
No. It excludes blog and store pages and should be combined with structured access and a live crawl.
The approved content model, templates, blocks, fields, plugins, and routes should be ready before production loading and visual acceptance.
Only after final transfer, redirects, files, launch checks, monitoring, rollback disposition, and required evidence are approved.
It identifies the boundary, but commerce data and behavior require a separate checklist and scope.
The pair page explains compatibility and mapping boundaries; this checklist coordinates evidence, owners, decisions, staging, cutover, and closure.
Next step
Turn the checklist into a scoped plan
Get an estimate based on the type, volume, and complexity of the data you want to migrate. Select the source and target systems, enter the migration details, and receive a calculated estimate. Online payment activation is being prepared. Until automated payment processing is available, plan activation and billing may be handled through a separate onboarding process.