<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/ead369817b2440fe9925c7f356a6a84b&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/ead369817b2440fe9925c7f356a6a84b-281079ca493d7079.gif</thumbnail_url><duration>227.243</duration><title>How to Migrate to Conduit v3</title><description>This Loom explains how to migrate a Conduit workspace to v3. In Settings under General, users scroll down, click Setup v3, check the box, and hit Migrate Me to start the migration, which moves global, inbox, property, and source knowledge verbatim into the new v3 knowledge base. The Operator agent handles the migration, including converting procedures into v3 skills similar to Claude procedures, with ability to call more tools. After migration, users can view the new folder-based knowledge base and then click Switch to V3 to redirect their team to v3.</description></oembed>