migrate-a-professional-portfolio

name	migrate-a-professional-portfolio
category	resume
description	Migrate a professional portfolio while preserving content, client rights, URLs, evidence, accessibility, analytics, contact behavior, and rollback. Use when changing portfolio platforms, domains, frameworks, or ownership.

migrate-a-professional-portfolio

Preserve visitor trust and client permissions, not just screenshots.

When to use

• Use when a portfolio's host, builder, CMS, framework, domain, account, or information architecture changes.
• Use ordinary editing when URLs, platform behavior, permissions, public evidence, and release operations remain unchanged.

Preconditions

• Confirm owner, domain and account control, source export, platform deadline, audience, release authority, client permissions, privacy, accessibility, and retention duties.
• Preserve source files, databases, exports, media, forms, analytics configuration, redirects, metadata, testimonials, permissions, versions, and a crawl of current URLs.
• Identify third-party embeds, fonts, code, forms, tracking, downloads, certificates, email routes, and credentials.

Procedure

1. Create a content and rights inventory for every case, page, asset, testimonial, logo, screenshot, download, author, client permission, license, retention rule, and disposition.
2. Crawl public and intentionally private routes and record titles, descriptions, canonicals, structured data, status, inbound importance, and indexed state.
3. Define URL and behavior mapping for pages, anchors, assets, navigation, filters, search, media, forms, downloads, contact, analytics, privacy choices, error states, and accessibility.
4. Decide keep, revise, combine, redirect, archive, restrict, or remove for each item without using migration to bypass consent or contract limits.
5. Build the target with semantic structure, responsive media, accessible interactions, privacy controls, security headers, performance budgets, and managed secrets.
6. Preserve source dates, contribution, outcome evidence, client attribution, and link context; label reconstructed or illustrative work.
7. Implement one-hop redirects and maintain canonical, sitemap, social preview, feed, and search behavior.
8. Run migration waves and parity tests for content, rights, links, forms, email delivery, downloads, analytics, SEO, accessibility, browsers, mobile, performance, and security.
9. Rehearse domain, DNS, certificate, form, email, cache, deployment, and rollback with measured recovery and no loss of new inquiries.
10. Cut over during a monitored window, verify from independent networks and devices, and retain the source until redirect, evidence, and rollback obligations expire.
11. Re-crawl after launch, inspect search and contact signals, correct failures, and document source retirement.

Failure plan

• If permission is absent or ambiguous, remove or restrict the affected material rather than assuming old publication permits migration.
• If a critical URL or contact path fails, pause or roll back before losing inquiries or public evidence.
• If the old platform blocks export, preserve lawful rendered evidence and metadata without scraping restricted data or credentials.
• If rollback would lose new form submissions, capture and reconcile them before switching.
• Never publish private drafts, client data, hidden analytics identifiers, source secrets, or expired testimonials.

Worked example

A consultant must move from a hosted builder before a custom domain expires. The site contains indexed case URLs, client logos under different permissions, private PDF links, dynamic embeds, a contact form, analytics consent, and incomplete backups. The team inventories every asset and right, removes an expired testimonial, maps routes and behaviors, rebuilds accessible cases, tests form delivery and analytics choices, and rehearses DNS rollback while preserving new inquiries. Independent crawl and contact tests pass before the old account is retired.

Done

• A portfolio migration register records content and rights inventory, custody, permissions, URL and behavior mapping, dispositions, owners, waves, and approvals
• A content and behavior parity report verifies migration waves and parity for content, links, rights, SEO, accessibility, forms, email, analytics, performance, security, and devices
• A cutover and rollback rehearsal proves domain, DNS, certificate, deployment, form and inquiry reconciliation, rollback timing, monitoring, redirects, and retirement gates