<?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/9ac97a1691004d7b860a6ddc1bba482f&quot; frameborder=&quot;0&quot; width=&quot;1728&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1728</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1728</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9ac97a1691004d7b860a6ddc1bba482f-418bac3a9d9c4951.gif</thumbnail_url><duration>371.188</duration><title>ChargeBee-Zenskar Migrator</title><description>In this video, I walk through the implementation of our migration process using the Charge B and Zinska APIs. I detail how I set up synchronous and asynchronous calls to efficiently handle customer and contact migrations, including logging and error handling. We successfully migrated 10 customers and 10 subscribers, and I demonstrate how to map responses for future use. I encourage you to review the migrated.log file for a detailed log of the process. Please let me know if you have any questions or need further clarification on any part of the implementation.</description></oembed>