Unlimited JPEG storage, galleries, portfolio, and selling

Treat a SmugMug move as an archive decision before treating it as a website project.

SmugMug includes unlimited full-resolution JPEG storage on its plans. Patsy makes no public launch claim for gallery or archive storage, so a safe plan keeps the current archive and client delivery in place while the public website is considered separately.

Before deciding

Know what the current platform is doing well.

A move is justified by a specific improvement, not by temporary frustration with one screen or one price increase.

Read Patsy vs SmugMug

Patsy's launch plans do not publish an active-delivery or archive-storage allowance. A storage-for-storage replacement should not be assumed.
SmugMug can combine portfolio presentation, private galleries, selling, and a large photo library. Those uses may need different destinations.
RAW storage is a separate SmugMug add-on. Confirm whether any originals outside the JPEG library are stored there and how the studio will preserve them.
Gallery URLs, folders, privacy, downloads, favorites, products, and order records require acceptance checks beyond verifying image count.

Collect before starting

The account is not the backup.

Create an independent record of files, active client promises, business data, settings, links, and ownership before cancellation becomes a deadline.

Total JPEG library size, folder and gallery count, approximate image count, RAW add-on use, and an independent original-file backup
A gallery inventory showing active client use, privacy, passwords, download rules, favorites, expiration expectations, and direct links
Portfolio pages, navigation, custom URLs, captions, keywords, search fields, brand assets, and featured-image choices
Products, price lists, lab choices, markups, taxes, shipping, coupons, orders, refunds, and unresolved client support
Domain, DNS, business email, analytics, search tools, custom code, embeds, and social or partner links
A written archive strategy distinguishing master files, backup copies, active delivery, public portfolio, and safe-to-retire work

Staged migration plan

Move the lowest-risk work first. Move the domain last.

Each phase has a result to verify before the next phase begins. Keeping the systems overlapped costs more briefly and can prevent much larger client-facing failures.

1. Measure the library before choosing a destination

Avoid discovering an archive-size mismatch after the project begins.

Record JPEG, RAW, folder, gallery, and approximate image totals.
Classify content as master archive, secondary backup, active client delivery, public portfolio, historical delivery, or safe to retire.
Document active-delivery needs and create a separate archive plan without assuming Patsy is the destination.

2. Rebuild the public studio first

Improve discovery and inquiries without forcing an immediate archive move.

Select the strongest approved work and provide original files, copy, services, specialties, locations, and policies.
Review the proposed Patsy website direction, inquiry path, search fields, mobile crops, image weight, and redirects.
Leave SmugMug galleries and storage live while the public site is tested.

3. Verify the active-delivery destination

Keep recent work on its current service until Patsy's private gallery and delivery tools pass the studio's own client test.

Keep SmugMug live for gallery delivery until a representative Patsy gallery passes every selected access, download, favorite, and ordering check.
Use a representative gallery with privacy, downloads, favorites, and products similar to current jobs.
Then test authorized access, image quality, mobile experience, ordering, payment, production information, and emails as a client.
Record missing behavior and decide whether to adapt, postpone, or keep that gallery on SmugMug.

4. Move only what has a safe home

Protect archives and clients while reducing platform dependence deliberately.

Move current galleries in controlled groups only after a verified destination passes every client test.
Keep large historical libraries on a verified archive system rather than forcing them into active delivery.
End the old plan only after files, records, links, orders, and retention obligations have been reviewed.

Be carefulA website launch does not require an archive migration on the same day. Separating those decisions is often safer.

Review manually

Data that rarely behaves like a simple file copy.

JPEG and RAW storage, folder structure, gallery hierarchy, filenames, captions, keywords, and metadata
Privacy, passwords, download sizes, watermarks, favorites, client links, expiration, and visitor expectations
Products, labs, price lists, markups, taxes, shipping, coupons, orders, refunds, and sales records
Portfolio pages, customizations, mobile layout, domain, search metadata, embeds, and direct gallery links
The distinction between master archive, backup, active client delivery, and public portfolio copies

Cutover checks

Evidence that the replacement is ready.

The studio has an archive plan that does not rely on any unverified Patsy storage allowance.
Original photographs are independently backed up and representative files match expected quality after transfer.
Before any future gallery cutover, a signed-out client can access, favorite, download, and order from the verified destination as intended.
No open order, unresolved support issue, or recent client link will be stranded by cancellation.
Public URLs, inquiry forms, domain records, email, analytics, search tools, and redirects work after launch.

Platform sources

Patsy and PA Digital Studio are not affiliated with SmugMug. Export tools and platform policies change, so confirm current documentation and account options before planning the move.

Ready when you are

See the replacement before moving anything out of SmugMug.

Build and review the public direction first. Keep the existing site, account, client galleries, and domain untouched until you deliberately approve a change.

See what Patsy can do for you