<?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/9aec58b7f221453f8174929ef29e9b6b&quot; frameborder=&quot;0&quot; width=&quot;1670&quot; height=&quot;1252&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1252</height><width>1670</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1252</thumbnail_height><thumbnail_width>1670</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9aec58b7f221453f8174929ef29e9b6b-22bda2b6e420f067.gif</thumbnail_url><duration>242.43</duration><title>Module 3A - Importing Premise/Sync Files into NextCity</title><description>This Loom explains how to import a premise or synchronization file from your CIS system into NexCity to keep customer and service account data in sync. It notes that the CIS system is the source of truth, and NexCity mirrors updates so changes like move ins, move outs, or address updates do not need to be made in two systems. In NexCity, the viewer goes to the Organization tab, then Settings, and runs the premise file import via the import configs menu. After downloading the premise file from the CIS vendor, the importer reviews updates such as six locations changed, including device ID updates, address corrections, premise ID corrections, and resident card customer name corrections, then applies the changes and shows a successful import message.</description></oembed>