How We Automated CRM Data Entry and Saved 2 Hours a Day

The Problem: 2 Hours of Copy-Paste Every Morning

A regional distribution company ran two parallel CRM systems during a migration period. The new system had better reporting; the old one had all the historical data. Every morning, a sales manager opened both apps side by side and manually typed 120-150 client updates from one to the other: names, phone numbers, deal stages, notes.

The task took between 90 minutes and 2.5 hours depending on overnight volume. Purely mechanical - the same sequence of clicks and keystrokes, repeated hundreds of times. A perfect candidate for macro automation.

The Solution Overview

We used Repio PRO to build a macro that:

• Opens the old CRM and navigates to the updates view
• Copies a record (Ctrl+A then Ctrl+C on each field)
• Switches to the new CRM (Alt+Tab)
• Creates a new entry and pastes each field in sequence
• Loops back to the next record in the old CRM

The entire macro file is 847 actions, runs in 8 minutes for 120 records, and requires zero interaction once started.

Step 1: Recording the Workflow

We started by doing the task manually while Repio was recording (F5 to start, F6 to stop). The key is to move deliberately - no rushed mouse movements, no accidental clicks. One complete record cycle: about 23 actions.

action_type,button,x,y,delay_ms,comment
move,,,1240,320,150,Navigate to client list
click,left,1240,320,200,Open first record
key,ctrl+a,,,50,Select all in Name field
key,ctrl+c,,,100,Copy Name
key,alt+tab,,,300,Switch to new CRM
click,left,890,440,150,Click Name field
key,ctrl+v,,,80,Paste Name

After recording one full cycle (one record from old CRM to new), we had the raw macro. Next: making it repeat.

Step 2: Adding the Loop

Repio's loop action repeats a range of rows N times. We wrapped the 23-action record sequence in a loop of 120 iterations. In the visual editor: select the rows, right-click, Add Loop, set count to 120.

One important detail: after processing each record, the macro needs to click "Next" in the old CRM to advance. We added a click action at the end of the loop body pointing to the "Next" button coordinates.

Step 3: Adjusting Timing

The initial recording had very long delays (we were thinking while recording). In the editor, we bulk-selected all move actions and reduced their delays to 80ms, and all key action delays to 50ms. Applications needed minimum 200ms after each paste to register input - we kept those.

Final timing: 4 seconds per record x 120 records = ~8 minutes total. Down from 90-150 minutes.

Results and Numbers

The macro paid for its setup time in a single day. The sales manager now starts it, makes coffee, and comes back to a fully synced CRM.

Tips for Similar CRM Cases

• Prefer keyboard over mouse: Tab-based navigation between fields is more robust than click coordinates when UI layouts shift.
• Add a bookmark (Ctrl+B in Repio) at the start of each loop iteration - if something fails at record 73, jump there directly instead of restarting.
• Test with 3-5 records first. Set loop count=5, check results manually, then scale to full count.
• Web hooks for dynamic counts: If the record count changes daily, use Repio's web hook feature to fetch the count from an API and use it as the loop limit.
• Handle popups: If the CRM occasionally shows confirmation dialogs, add a conditional click action to dismiss them before continuing.