Quick answer: export a Final Cut Pro XML from a clean copy of the locked Premiere Pro sequence, send the original media with it, and add a reference movie. Import the media and the XML into a Resolve project that's already set up correctly, then compare the conform shot by shot before anyone grades a frame. XML carries timeline decisions. It doesn't carry the source files, the full Premiere project or every effect.
Keep that split in mind and most failed handoffs never happen. Getting a timeline to show up in Resolve is the easy part. The real job is proving that each event points at the right source clip, uses the right in and out frames, and matches the approved edit closely enough to start color or finishing.
If you're still deciding which editor should own the project, read the broader DaVinci Resolve versus Premiere Pro comparison first. Everything below assumes the edit already lives in Premiere and now has to move.
What XML Transfers From Premiere to Resolve
Premiere Pro and DaVinci Resolve don't share a native project format. XML is an interchange file that describes part of a sequence: clip placement, source references, tracks, edits and some basic transitions and transforms.
It does not contain the camera originals. Daniel Grindrod's Premiere-to-Resolve workflow from Daniel Grindrod says it plainly: the XML stores timeline data, and the media has to be transferred and relinked separately.
Expect these to need inspection, a rebuild or a render:
- nested sequences;
- multicam structures;
- Dynamic Link compositions;
- Essential Graphics and complex titles;
- adjustment-layer effects;
- third-party plugins;
- masks and effect-specific keyframes;
- Warp Stabilizer and other analysis-based effects;
- complex speed ramps, reverse clips and freeze frames;
- audio effects, automation and nonstandard channel mapping.
Simple dissolves, clip positions and scale values often come through, and Blackmagic's manual lists opacity, position, scale, rotation and both linear and variable speed effects among the XML data Resolve reads. Nice to have. It still doesn't let you skip the conform pass, because what survives depends on the edit itself, the media, both application versions and how each effect was built.
Decide What the Handoff Must Achieve
A handoff usually ends in one of three places.
Color in Resolve, Then Return to Premiere
Premiere stays the finishing application. Resolve gets a simplified sequence and the original media for color, then renders graded clips, usually with handles for the transitions, plus interchange data for the return.
This keeps graphics, captions, editorial effects and the final mix in Premiere. It also means a second conform when the graded media returns, so file naming and source identity have to stay under control the whole way.
Finish the Project in Resolve
The XML transfer is one-way. After the conform, Resolve owns color, final picture, audio finishing and delivery. Titles and effects that don't translate get rebuilt in Resolve or arrive as rendered assets.
You lose the return trip, not the prep. A bad conform is still a bad place to start.
Move the Editing Workflow to Resolve
This is closer to a migration than a color handoff. XML can move the timelines you pick, but bins, markers, custom metadata, graphics templates, effect setups and project organization won't turn into a finished Resolve project on their own.
Move the sequences that matter, rebuild the project organization on purpose, and keep the Premiere project as the archive of record until the migration is signed off.
Duplicate and Lock the Premiere Sequence
Never simplify the only copy of the approved edit. Duplicate the picture-locked sequence and give the copy an obvious handoff name. The UT Austin Premiere-to-Resolve workflow follows the same pattern, and it has held up for years: duplicate the final sequence, prepare that copy, then export both the XML and a reference movie.
Before you touch the handoff copy:
- Save the Premiere project as a new version.
- Confirm the approved sequence's start timecode and duration.
- Clear out disabled experiments that aren't part of the handoff.
- Label every shot or section that will be rendered, not translated.
- Leave the original locked sequence alone for comparison.
Picture lock doesn't mean the cut can never change. It means the transfer has one declared version. If the sequence changes after the XML export, build a new handoff package; don't quietly swap one file inside the old one.
Reconnect Full-Resolution Originals
Don't assume an attached proxy means Resolve will find the matching camera original. Adobe's guidance for reconnecting full-resolution media to proxies explains how Premiere keeps proxies tied to the full-resolution files and how to reconnect those originals. Use that link before you export, then check it.
Spot-check clips from every camera, every shoot day and every storage root:
- the full-resolution file is online;
- frame size and frame rate match the intended source;
- source timecode is there where you expect it;
- the audio channels are the real originals;
- the clip isn't linked by accident to a proxy, a transcode or a duplicate file with the same name.
A proxy-only conform can look fine at first and still lock you out of RAW controls, resolution-dependent reframing or final delivery. If the originals can't travel, set up the replacement media as a formal intermediate workflow. Don't let Resolve grab whatever file happens to match.
Simplify Structures That Do Not Travel Cleanly
The safest handoff copy isn't always a one-track timeline, but every layer in it should have a clear job.
Multicam
Flatten multicam edits when the receiving editor only needs the chosen angles, and keep the original multicam sequence in Premiere. After flattening, spot-check the cuts around angle changes and make sure the flattened clips point to the intended camera files.
Nested Sequences
Open each nest and decide whether Resolve needs the editable structure or just the final picture. A nest of ordinary cuts can be expanded. A nest that holds stabilization, compositing or motion work is usually safer as a rendered replacement.
Adobe's Render and Replace documentation describes a reversible way to flatten clips, After Effects compositions and nested sequences into replacement media. Use it on the handoff copy when the translation risk outweighs the value of keeping that structure editable.
Graphics, Titles and Captions
If Premiere will finish the project, disable graphics in the color handoff and keep them in the locked master. Leave them in the reference movie so the colorist can see the approved composition.
If Resolve will finish, send editable text, fonts, logos and source graphics separately, or render the element with an alpha channel if that's the agreed delivery. An Essential Graphics template won't rebuild itself from XML.
Effects and Stabilization
Sort every effect into one of four buckets:
- remove it, because it's editorial-only;
- rebuild it in Resolve;
- render it into a high-quality replacement;
- keep it as a visual reference only.
Stabilization needs a decision made out loud. If it gets rebuilt in Resolve, keep enough source range and follow the Resolve stabilization workflow after the conform. If the exact Premiere result is approved and has to survive, render that shot and archive the unrendered source.
Retimes and Freeze Frames
Simple constant-speed changes can come across, but every retime still gets compared. Speed ramps, reverse motion, optical-flow work and freeze frames are where conforms most often go wrong.
For a complex retime, send both the original source and a high-quality reference or replacement render. The reference proves the timing; the original keeps your grading options open.
Export the XML and Read the Report
With the handoff sequence active in Premiere, export Final Cut Pro XML into a fresh package folder. Adobe's XML export documentation explains that Premiere can produce a Translation Results report when parts of the sequence can't be translated.
Read that report. It's a to-do list, not a receipt you can close and forget.
For every warning, find the affected clip or event and pick one of four actions:
- accept the translated result and check it in Resolve;
- simplify the event in the handoff copy;
- render a replacement;
- note that it has to be rebuilt after import.
Tie the XML filename to the sequence version. A name like project_picture-lock_v12_resolve.xml beats final.xml every time, because it tells everyone exactly which editorial state they're holding.
Create a Reference Movie
Export the reference movie from the untouched locked sequence, not from the simplified handoff copy. It should match the planned Resolve timeline in start timecode, frame rate, frame size and duration.
When you can, burn in source or sequence timecode and a small version label. Keep the picture clean enough to judge framing, cuts and transitions. Audio helps with sync even if Resolve will never see the final mix.
A practical Adobe Community accepted answer recommends sending XML or EDL together with a reference export and then checking cuts, sizing and speed changes. The reference movie is the visual contract. Without it, an imported timeline can look perfectly plausible while using the wrong frames.
Transfer the Media Deliberately
Besides the XML and the reference movie, the package needs source media. Pick one route:
- send the original camera and audio files with their folder structure intact;
- collect only the media the locked sequence uses, through a controlled media-management pass;
- transcode to agreed finishing media when the originals can't be used directly.
Keep the folder hierarchy whenever file names repeat. Camera cards love to restart names like C0001, and a flattened folder can end up with several unrelated files under the same base name.
Write a short manifest with the intended media root, codec, frame-rate policy and any rendered replacements. The receiving editor shouldn't have to guess which of three similar folders is the real one.
Configure Resolve Before Import
Start a fresh Resolve project for the conform and set the timeline frame rate and resolution before you build anything. Some timing decisions get expensive to change once editing has started. The Load XML dialog also has an Automatically set project settings option that copies the XML's frame size and frame rate into the project; that's fine when it agrees with your plan, so look before you click OK.
If the project mixes frame rates, decide whether each clip plays at its recorded rate, conforms to the timeline or is meant as slow motion. The separate DaVinci Resolve frame-rate guide helps when the transfer includes mixed or ambiguous footage.
Variable-frame-rate phone and screen recordings need extra care, because their nominal metadata may not describe every frame interval. Convert them to a suitable constant-frame-rate intermediate before the interchange when sync or source timing is shaky.
Import the original media into organized bins, then bring the XML in as a timeline. The Load XML dialog's Automatically import source clips into media pool checkbox decides how media gets found: on, Resolve follows the paths stored in the XML and asks for a folder when it can't find them; off, it conforms to clips already in the Media Pool. With duplicate names, importing and sorting the known media first and leaving that box off makes the relink much easier to audit.
Relink Without Choosing the Wrong File
An offline clip is obvious. A wrong but successful relink is worse, because it can ride along all the way to export.
When the XML points at missing paths, relink to the declared media root. If several files share a name, look past the filename:
- source timecode;
- reel or tape metadata;
- camera and card folder;
- duration;
- resolution and frame rate;
- audio channel count;
- source in and out frames.
Offline clips show up red on the Resolve timeline, and filtering the Edit Index for offline clips lists them in one place. If some stay unavailable, the Media Offline troubleshooting guide helps separate a path problem from unsupported media, permissions, storage mounts or bad metadata. Don't start grading around offline events you can't explain.
Run a Shot-by-Shot Conform Pass
Resolve has a built-in way to do this. Link the reference movie to the imported timeline (right-click the timeline in the Media Pool and use Timelines > Link Offline Reference Clip), then switch the Edit page Source Viewer to Offline mode. Both playheads move together, and right-clicking the Timeline Viewer gives you wipes and a Difference view. The manual's one condition is timecode: the reference has to start where the timeline starts, though a small offset can be slipped in the Source Viewer's sync field. Stacking the movie on a track above the cut still works too. The method matters less than checking every event.
Go through the sequence in passes.
Pass 1: Clip Identity and Cuts
Confirm that every shot uses the correct source file and that each cut lands on the same frame as the reference. Check the first and last frame of every clip, not only the middle.
Watch repeated takes, duplicate file names, flash frames, one-frame edits and shots that came out of multicam sequences.
Pass 2: Framing and Transforms
Compare scale, position, rotation, crop and opacity. The Load XML option Use sizing information brings Premiere's position, scale and rotation into each clip's Inspector, but Premiere's scaling choices can still land differently in Resolve, especially when source resolution differs from sequence resolution.
Don't fix framing by eye before you know the cause. A global scaling mismatch calls for one consistent policy; a single odd reframe calls for a clip-level fix.
Pass 3: Retimes and Transitions
Check every constant-speed change, ramp, reverse clip, freeze frame and optical-flow shot. Resolve converts a variable-speed effect into a speed keyframe on every frame, and the manual warns that small differences against the reference movie appear when the Retime Process setting doesn't match the interpolation Premiere used. Compare each transition's start, end and duration, and confirm there are source handles on both sides of every dissolve.
If the imported retime won't match reliably, rebuild it from the original source or drop in the approved replacement render. Write the choice down.
Pass 4: Effects and Graphics
Make sure every event marked for rendering or rebuilding has actually been dealt with. Don't grade a placeholder as if it were the final composite.
If graphics will return to Premiere, use the reference movie to see where they sit and keep them out of the color pipeline.
Pass 5: Audio and Sync
Listen at the beginning, middle and end of long clips. Check separately recorded audio, multicam sync, muted regions, channel mapping and any audio edit that doesn't line up with a video cut.
The reference mix won't stand in for the final audio session, but it's the quickest way to catch a shifted edit or a clip linked to the wrong source.
Fix Common XML Transfer Failures
The Timeline Imports but Most Clips Are Offline
Either the XML arrived without its source media, or Resolve can't resolve the old Premiere paths. Confirm the package holds the intended originals, then relink from the highest useful common folder. Don't search an entire workstation when there's a controlled media root.
Resolve Links to the Wrong Shot
Look for duplicate base names, stripped card folders, overlapping timecode or missing reel metadata. Unlink the wrong media and relink from the specific camera or card folder. Check the source in and out frames against the reference before moving on.
Framing Is Different
Compare source resolution, timeline resolution and the scaling method used in Premiere. Then check whether Use sizing information was on during import and what the project's Input Scaling setting for mismatched resolution files does to those clips. Decide whether the project needs one consistent input-scaling rule or individual transform fixes, and check any shot that was resized inside a nest.
Retime Events Drift or Use the Wrong Frames
Rebuild the retime from the original source or replace it with the approved render. Confirm the timeline and source frame rates, and set the Retime Process to match Premiere's interpolation before you touch the speed. A timing fix made under the wrong frame-rate assumption just creates a second error.
Nests, Graphics or Effects Disappear
Return to the handoff copy and simplify, expand, render or document the element. Don't patch a missing composite with the reference movie unless the reference was deliberately made as the finishing master.
The Edit Is Too Complex for a Clean XML Conform
Use a high-quality flattened master as a controlled fallback. Resolve can cut a rendered master back into shots with Scene Cut Detection: on the timeline through Timeline > Detect Scene Cuts, which the manual marks as Studio-only, or with the original Scene Detect tool in the Media page. The reference and the original project keep the editorial intent. You give up source handles and most of the clip-level flexibility, so take this route only when rebuilding the interchange would cost more than those losses.
Finish in Resolve or Return to Premiere
If Resolve owns final delivery, save a clean conform version before grading. That version becomes your baseline for any later troubleshooting. Do the color, effects, audio and delivery work on a duplicate or a later project version.
If the project returns to Premiere, agree on the delivery before you render:
- individual graded clips or one flattened master;
- file naming and destination folders;
- source resolution and frame rate;
- codec, bit depth and alpha requirements;
- audio included or left out;
- handle length for transitions;
- XML or other interchange data for the return;
- how speed effects and rendered replacements are handled.
Once the graded media is back in Premiere, run another conform against the locked master. Check cuts, transitions, retimes, graphics and the final audio before you export.
Premiere-to-Resolve Handoff Checklist
Before color or finishing starts, confirm:
- the handoff sequence is a duplicate of the approved locked edit;
- the original Premiere sequence hasn't been touched;
- full-resolution media is online and nobody is mistaking proxies for masters;
- multicam, nests, graphics, effects, stabilization and retimes each have an explicit plan;
- someone has read Premiere's Translation Results report;
- the package holds the XML, the reference movie and the intended media;
- timeline frame rate, resolution, start timecode and duration are written down;
- Resolve links every event to the correct source clip;
- cuts, framing, transitions, retimes and audio match the reference;
- every discrepancy is fixed or documented before grading;
- everyone has agreed in advance whether Resolve or Premiere finishes the project.
A clean XML import is only the start. The handoff is ready when the imported timeline survives a shot-by-shot comparison with the locked reference and every exception has an owner.
