Inventory
List domains, pages, blog posts, forms, contacts, active jobs, contracts, invoices, galleries, downloads, favorites, orders, automations, and external integrations.

Move the studio without disrupting the studio
These guides help photographers inventory what they have, protect active client work, test the replacement, and move in stages. They are planning guides, not claims of one-click imports.
Platform-specific checklists
Every platform stores different combinations of pages, images, galleries, favorites, contracts, invoices, orders, contacts, domains, and search value. A safe plan begins with that difference.
Back up website copy, blog content, portfolio images, client records, contracts, and gallery originals.
Open the migration guide ›Gallery and print-sales platformUse Pic-Time's export and migration options to preserve originals and client information where available.
Open the migration guide ›Galleries, selling, and studio toolsInventory all galleries by photo count, expiration, download rules, and client status.
Open the migration guide ›Photo storage, portfolio, and sellingTreat SmugMug as the photo archive until every original is independently backed up.
Open the migration guide ›General website and commerce platformExport site copy, blog posts, media, form contacts, commerce data, analytics, and URL structure.
Open the migration guide ›Open publishing software and hosted website platformExport the database, media library, posts, pages, users, forms, SEO metadata, and redirects.
Open the migration guide ›The universal migration sequence
The safest order is usually public site first, then new inquiries, then future bookings, then active client delivery, and only then older records or archives.
List domains, pages, blog posts, forms, contacts, active jobs, contracts, invoices, galleries, downloads, favorites, orders, automations, and external integrations.
Keep independent copies of original photographs and export every available business record before relying on any new platform or migration process.
Decide what recreates cleanly, what can import, what must remain available in the old system, and what should be retired rather than carried forward.
Create the new site and workflow without changing DNS, interrupting client links, or cancelling the existing service.
Test mobile pages, forms, replies, booking, payments, gallery privacy, downloads, orders, redirects, domain records, analytics, and email delivery.
Move only the verified path, monitor it closely, and keep the old service available until every active client and business dependency is accounted for.
Migration checklists, content inventories, URL maps, and staged launch planning can be prepared before you commit. A current platform can stay live while the public Patsy direction is reviewed.
Hands-on migration is separate work and is quoted before it begins. Scope depends on the old platform, available exports, data volume, active client work, custom integrations, and what has been verified end to end.
Do not cancel yet
Ready when you are