Switch photography software without moving everything at once

Software migrations often begin with the archive because the archive feels measurable. It has folders, records, and a visible finish line. But moving old data does not prove that the next live job will work better.

A safer switch begins with one representative project.

In Still Bureau, contacts and projects can be tested during the 14-day Studio trial and are not included on Free afterward. The website and gallery workflow remains available on Free within its published limits. This article's studio-workflow examples should be read with that boundary in mind.

Choose a useful test job

Pick current work with a real deadline but enough room to recover if a step is awkward. The project should include the workflows that matter most: an inquiry or contact, a project record, a gallery, client review, and final delivery.

Do not choose the easiest possible job if it avoids the reason for switching. Do not choose the most sensitive or complex job either. A representative middle case reveals more.

Define the exit criteria

Before importing anything, list what the new system must prove. Examples include publishing a branded page, uploading ten representative photographs, receiving a client favorite, collecting an image-level comment, delivering a gallery ZIP of up to 1,000 photos, and finding the project record later.

Include the mobile client experience and the studio’s own daily view. A workflow that looks good publicly but adds hidden administrative work has not passed.

Keep the scorecard small enough to finish. For each requirement, record the exact route tested, what happened, and one of three decisions: pass, workable with a documented step, or stop. “It seemed fine” is difficult to compare later.

Move the minimum viable context

Create the contact, project, and one gallery. In Still Bureau, those records do not associate themselves: a studio user must choose the project on the gallery and save that relationship. There is no automatic archive migration in this test. Upload a small real set whose usage rights are clear. Recreate only the templates or branding needed for the test. Keep the old system available during the overlap.

Avoid duplicate live messages. Decide which system will send client communication for the test job, and send from that one.

Exercise the handoffs

Follow the project from the studio side to the public side and back. Confirm the manually associated gallery appears on the intended project. Use a separate browser or device as the client. Leave a favorite or comment. Download the promised file. Confirm the result appears where the studio expects it.

Test a personal gallery invite before involving a client: send it to an address the owner controls, open the exact URL without the owner session, forward it to a second controlled address, and verify revocation separately. A personal invite is revocable, but its URL is forwardable; it is not proof of the viewer’s identity.

Record friction as it occurs: repeated data entry, missing context, unclear states, or tasks that require an unsupported workaround. Compare those observations with the reason for considering a switch.

Decide what deserves migration

After the live test, separate active records, reference records, and archives. Active projects may need a complete move. Reference data may need a clean export that remains searchable. Old galleries may be safer in read-only storage until their promised delivery periods end.

The right outcome is not necessarily “move everything.” It is “preserve what the studio is obligated to keep and move what improves future work.”

Incremental switch checklist

• One representative project and recovery path are chosen.
• Success criteria cover both studio and client behavior.
• Each result is marked pass, workable with a documented step, or stop.
• Only the minimum useful context is recreated.
• The gallery is manually associated with the intended project and both views are checked.
• One system sends the live client communication.
• The exact public, personal-invite, and download paths are tested with owner-controlled addresses before client use.
• Friction is recorded during the work, not reconstructed later.
• Active, reference, and archive data receive different migration decisions.

If the test passes, move the next active job. Leave the archive decision until the new workflow has earned it.