Studio workflow migration
Move from Dropbox or gallery handoffs without disrupting the studio.
Map the process you already use, move one real job first, and replace manual handoffs only after the new proof-to-delivery workflow proves itself.
Selected proof portrait-014.jpg
Client note
Use the natural crop and keep the standard studio finish.
Next handoff Upload finished master Prepare full-size and profile-ready versions after review.
Representative product view using sample names and files. It demonstrates the shipped workflow stages without exposing a client gallery or implying a customer result.
Start with an audit
Document the real process, including the work between tools.
A studio may use Pixieset for galleries, Dropbox for final folders, email for selections, and a spreadsheet for retouching status. The visible tools are only part of the system; saved templates, filename rules, and staff habits also need to be mapped.
This guide does not assume that every existing tool should be removed. The goal is to identify the manual handoffs that create uncertainty and test whether one connected workflow handles them better.
- Where proofs are uploaded
- How clients receive access
- How favorites become confirmed choices
- Where retouching notes are stored
- How finals are named, packaged, and delivered
- How the studio verifies download and follow-up
Protect active work
Do not move a client job simply to make the migration look complete.
Keep active gallery and download links working through their promised access window. Export the records you may need later, and avoid changing a client-facing process in the middle of retouching unless there is a clear operational reason.
Choose a new or low-risk representative job for the first LumenProof run. It should exercise the studio's normal selection and delivery needs without carrying unusual complexity.
Review the result
Compare the whole job, not the upload screen.
After the first delivery, review how many manual messages were required, whether the submitted selection was unambiguous, whether retouching received a complete brief, and whether the client understood the final package.
Expand only when the new process is clearer for both sides. A staged migration is more credible than a forced switch, and it preserves a straightforward rollback path.
- Selection record was complete
- Retouching began without clarification
- Final package matched the agreement
- Client retrieved the delivery successfully
- Studio knows what it would change next time
FAQ
Questions about this studio workflow.
Does this guide compare every Pixieset or Dropbox feature?
No. It focuses on the studio's proof-to-delivery handoffs. Existing platform features and pricing can change, so the migration decision should be based on the current tools and the studio's real workflow.
Should active client galleries be moved?
Usually not. Preserve active links through the promised access period and start the new workflow with a suitable new job unless there is a specific reason to migrate an active one.
What should the studio export before switching?
Keep the records the studio relies on, such as client contacts, submitted selections, retouching notes, final filenames, saved messages, and delivery history, subject to the studio's privacy and retention policies.