
Do not assume a Frame.io Legacy integration continues unchanged after moving to V4. The captured Frame.io migration guide lists DaVinci Resolve integration as unsupported and points to importing comments in EDL format as an available handoff approach. Treat that as a documented transfer to verify against the actual reviewed cut, not automatic two-way synchronization.
Key Takeaways
- Confirm the account generation and current integration support first.
- Preserve the reviewed movie and original comments before transferring feedback.
- Check imported note locations against the exact Resolve timeline version.
Identify the changed integration boundary
The official Free, Pro and Team V4 migration guide documents changes from Legacy, including unsupported integrations. It also warns that features may change through subsequent updates. Check the current supported route for your account and installed editor rather than repeatedly reconnecting an obsolete workflow.
A missing integration does not establish that the video or comments have disappeared. Open the relevant review destination and confirm the underlying asset and feedback remain accessible through authorized access. Avoid disabling project restrictions to repair an integration issue.
Freeze the review reference before exporting notes
Record the movie's revision, duration and time reference. Keep a copy of the reviewed export and the original comments in an approved location. The approved-version handoff record provides a way to connect these items.
Do not recut the opening while creating the feedback transfer and then expect every old timestamp to remain correct. A note can be textually intact yet point to a different scene in the new timeline.
The source-versus-sequence timecode guide explains that reference distinction using Premiere. The principle is relevant here, but its menu instructions do not apply to Resolve.
Test the supported comment transfer on a duplicate
Use the current supported Frame.io comment-export and Resolve import controls for the documented EDL route. The migration overview is not a complete command reference, so inspect the actual available choices rather than inventing menu names. Preserve the original working timeline.
A proposed verification sequence is:
- Identify the exact Frame.io asset and review revision.
- Obtain the supported comments handoff file and retain its source association.
- Import through the appropriate Resolve workflow into a duplicate or controlled timeline.
- Check an early, middle and late note against the reviewed movie.
- Compare note wording, requested action and the picture at each location.
For a hypothetical portrait edit, a note about a blink near the ending must still point to that blink, not just to a plausible nearby face.
Resolve mismatches without shifting everything blindly
If all sample notes differ, check the reviewed revision and time origin before adding an arbitrary offset. If only one note differs, inspect its own interval and source context. Do not claim a successful import preserved attachments, replies or every comment property unless the actual transfer confirms it.
Keep reviewers on one clearly designated destination. A manual EDL handoff does not prove that later comments or resolved statuses synchronize back. The review-copy versus master guide helps state which cut remains under review. Accept the transfer when the editor can locate and act on the intended feedback, with unsupported or unverified fields explicitly retained in the original record.
Related tasks
- Which Timecode Should I Send When Requesting a Premiere Shot Revision?
- Should I Send a Review Copy or the Final Master of an AI Video to a Client?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- Frame.io: What to expect when updating to V4 on a Free, Pro or Team plan: The captured V4 migration guide lists DaVinci Resolve integration as unsupported and identifies importing Frame.io comments in EDL format as a continuing handoff option. The guide cautions that support can change through future updates.
Based on the complete official migration source captured October 29, 2026. No migration, EDL export/import, Resolve timeline or synchronization was tested. Manual handoff steps are proposed checks; exact exporter/importer commands and an automatic two-way sync are not asserted because the supplied source does not establish them.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.