Keep Moving Files,
or Connect the Systems?
Almost every business starts here: export a spreadsheet from one system, tidy it up, and import it into another. It works, it costs nothing to set up, and it quietly depends on one person remembering the steps. The question is when that routine stops being cheap.
The Short Answer
Keep the manual export when it happens rarely, the file is small and a day-old copy of the data is fine. Connect the systems when the transfer happens daily or weekly, when someone has to clean the file before it will import, or when decisions are being made on numbers that are already out of date.
Side by Side
| Consideration | A system integration | Manual export and import |
|---|---|---|
| How current the data is | Updated as changes happen, or on a set schedule. | As current as the last time someone ran the export. |
| Staff time | None for the routine transfer; people review only exceptions. | Minutes to hours every cycle, forever. |
| Cleaning the file | Formatting and matching rules are built in once. | Redone by hand each time, often differently. |
| Errors | Records that fail a check are held and reported. | A wrong column or a duplicate import can go unnoticed. |
| When the person is away | Keeps running on schedule. | Waits until they are back, or someone guesses the steps. |
| Setup cost | A scoped build. | Nothing up front. |
Which One Fits?
An integration is likely the better choice when
- The transfer happens daily or weekly
- The file needs cleaning or reformatting before every import
- Decisions depend on data being current
- Only one person knows how to do it
Export and import is likely enough when
- It happens a few times a year
- The file imports cleanly with no editing
- Yesterday’s data is perfectly fine for the purpose
- One of the systems is about to be replaced
Four Questions That Decide It
Ask these about the export and import routine your team runs today.
How often does it run?
Multiply the minutes per cycle by the cycles per year. Include the cleanup, not only the clicks.
What goes wrong?
Duplicate imports, missing rows and mismatched columns each create cleanup work downstream. Count how often they happen.
How old is the data when it matters?
If people act on numbers that are days old, the delay has a cost even when the file is correct.
Is there an API?
Most modern business software offers one. Where it does not, a scheduled file transfer with checks is still far better than a manual one.
A Scheduled File Can Be the Middle Step
An integration does not always mean a live connection. When a system only offers file exports, the practical fix is to automate the file itself: pick it up on a schedule, clean and check it the same way every time, load it, and alert a person when something does not match. You keep the simplicity of files and lose the manual routine.
Typical Starting Points
Work is priced by scope, not by the hour. You get a written scope with a fixed price before anything starts, and larger builds are split into milestones. The ranges below show where engagements typically start.
See Starting Prices
| Engagement | When it fits | Investment |
|---|---|---|
| Automation Opportunity Review | You know the workflow hurts, but not yet what, if anything, to build: one workflow reviewed, with the smallest worthwhile fix in a written action plan. | $495 fixed fee |
| Quick Win Automation | One tightly bounded problem with a clear finish line. | From $1,500 |
| Core Automation or Integration Build | Workflows and system connections the business runs on, priced in a written scope. | From $5,000 |
| Operations Automation Partnership | After a build: monitoring, maintenance, vendor and API changes, and small improvements. | From $750 / month |
Hosting, domains, licenses, subscriptions, and processing fees stay in accounts you own and are billed to you directly by each vendor whenever practical. Where we must place an approved charge on your behalf, that amount is collected before we incur it.
After the Build
Every build ends with documentation and a handoff, so your team can run it. If you would rather not, a monthly partnership covers monitoring, vendor and API changes, and small improvements under its own written agreement.
See Partnership LevelsRelated Problems and Services
Before You Decide
- Is manual export and import really a problem?
- Not always. For an occasional, clean transfer it is sensible. It becomes a problem when it repeats often, needs hand cleanup or depends on one person.
- What if one of our systems has no API?
- We can often work with scheduled exports, database access or the vendor’s import tools, with checks added. We explain the trade-offs before you commit.
- Will an integration change how our team uses the software?
- Usually very little. The screens stay the same; the data simply arrives without someone moving it.
- How do we know the integration moved everything correctly?
- Every run is logged with counts of records moved, skipped and held, and failures alert a person, so a missing record is visible rather than silent.
- What does it cost to find out whether it is worth it?
- The Automation Opportunity Review puts the annual cost of the current routine and an implementation range in writing before any build.
This page is general information to help you compare options, not legal, financial, tax, employment or other professional advice. Figures are illustrations based on the stated inputs, not client or market data, and are not a promise of savings. We do not guarantee any particular business, time-saving or technical outcome. Our Terms of Service govern.
Full terms: Terms of Service
Tired of the Weekly Export?
Tell us which systems the file moves between and how often. We will tell you whether it is worth connecting them.