Why the copying starts
Nobody plans to copy data by hand. It starts with two tools that do not talk to each other: orders in one system, the team's tracker in a spreadsheet. Or a weekly report that needs numbers from three exports. Or one customer list kept in two places, because two teams use two tools.
Each copy takes a few minutes, so it never looks worth fixing. Over a year it adds up to days of work, and the cost is not only time. Retyped data picks up typos, rows go stale when the source changes, and the same customer appears twice under two spellings. The report is then right only as often as the copying is.
Step 1: decide where each piece of data is entered
Before changing any tool, write down where each kind of information is first entered: the order system for orders, the shared sheet for project status, and so on. That place is the source of truth. Every other copy should read from it, never be typed into by hand.
If a piece of data is entered in two places today, pick one and make the other read-only. This step alone often removes half the copying, because people stop updating the same thing twice.
Step 2: use what your spreadsheet already does
Both common spreadsheets can pull data from somewhere else, so the copy happens without anyone retyping it.
In Google Sheets, IMPORTRANGE brings a range from another spreadsheet into yours, and QUERY or FILTER can narrow it to the rows you need. In Excel, Power Query (Data, then Get Data) can load CSV exports, combine all the files in a folder and refresh with one click.
These work well for one-way transfers between files you control. They are fragile when someone renames a column or moves a tab, and they need someone to notice when a refresh fails. Keep a short note in the file that says where each imported range comes from.
Step 3: connect the apps, not the sheets
When the data starts in a web application, such as a form, a shop or a CRM, an integration tool can move each new record into the place it is needed. Zapier, Make and n8n are the best known. They suit simple rules: when a new order arrives, add a row.
Check three things before you rely on one: what happens when a step fails, who is told about it, and whose account the integration runs under. An automation that stops quietly is worse than the copying it replaced, because everyone assumes it still works.
Step 4: add a check before the data is used
Moving data automatically is half the job. The other half is knowing the result is right before it goes into a report, an invoice or an email. A check can be simple:
- Required fields are filled in, and dates and amounts have the right format.
- No record appears twice, even with a different spelling or extra spaces.
- Totals match the source, so nothing was dropped on the way.
- New and changed records are listed separately, so a person can look at what is different since last time.
When to automate it properly
Built-in imports and integration tools cover many cases. A small purpose-built tool is worth it when the copying involves several sources, cleaning rules, duplicates that need judgement, or a report that has to be right every week.
That tool reads the exports or connects to the systems, cleans and joins the data, removes duplicates, runs the checks and writes the result, with a short report of anything it could not handle. Our project Scout works this way: it collects listings from several sources, removes duplicates and reports only what actually changed.
This is the kind of job our workflow automation work starts with. The smallest version, Workflow Fix, is one task automated end to end, with a check step and handover notes, for a fixed price agreed before any work starts.
What to write down before you start
Whether you fix it yourself or ask for help, four answers make the work much easier: which task is done by hand and how often, where the data lives, what a good result looks like, and when you need it. Our guide on writing a software brief has examples.