---
title: "Switching From Elec_Test to Capps_Client"
space: "Wiki"
url: "https://www.sapconinstruments.com/wiki/switching-from-elec_test-to-capps_client"
updated: "2026-10-18"
---

<h2>Reason</h2>
<p style="text-align:justify;">Switching from Elec_Test to Capps_Client was necessary. Here is why:</p>
<ul>
    <li> Ease of Deployment </li>
    <li> Clean Code </li>
    <li> More Versatile Approach</li>
</ul>

<h3> Ease of Deployment </h3>
<p style="text-align:justify;">Capps Client is open source, which makes it easy to get tags from the git repository. This makes it more convenient to use remotely and easier to deploy.</p>

<h3> Clean Code </h3>
<p style="text-align:justify;"> It is basically the last tested version of Elec Test v2.0 but with proper arrangement of all related modules and more coder/developer friendly. </p>
<h3> More Versatile Approach</h3>
<p style="text-align:justify;">It is aimed to have multiple projects under one roof : Capps Tower, Capps Door, Dashboard and Getts. Currently it has Capps door and tower together. Dashboard is ready to be part of Capps_Client.</p>

<h2>Procedure</h2>
<p style="text-align:justify;">Here are the steps which will make migration more easier and simpler.</p>
<ul>
    <li>Keep elec test online with openrport running. </li>
    <li>Load script "migrate_elec_test_to_capps" and select all targeted elec_test clients by group or tags. (Don't forget to check execute concurrently) </li>
    <li>Execute that script and observe output of each client.</li>
    <li> It will migrate to Capps_Client with ease.</li>
</ul>