Your path: a smooth migration
The HC24 data bridge keeps Access and the CRM in sync until your team has fully switched — no big bang, no cut-over risk.
Replace Access
Replace your Access database — without losing your workflows
Your Access solution served you well — now it slows you down. We move data, forms and VBA logic into a modern CRM without your team starting over.
Module by module
What your Access modules become
Every grown database is made of the same ingredients — each has a clean successor in the CRM world.
Contact and company tables
Become the Act! data model with history — we clean duplicates during the move.
Outlook macros (VBA)
Replaced by Innlook: emails land on the right contact automatically — no custom code.
TAPI dialers and call lists
GiPhone takes over as SIP telephony: start and log calls right on the record.
Access reports
Become reports on demand — from data that is maintained anyway.
Import and export scripts
Run through maintained interfaces instead of one-off scripts on a server.
Input forms
Become CRM forms — plus mobile capture on the go, for example with GiContact.
How we work
Understand first, then replace — never the other way
A typical project starts with an inventory: which tables, forms and VBA modules exist, and which do you actually still use? We then map the data model in the CRM and migrate the data in a test run. Your team works in both worlds during a parallel phase until everything fits — only then is the old database switched off. Modules no standard tool covers, we rebuild as a tailored extension.
A fixed step in the process: data validation. Every record is checked on the way over — required fields, formats such as phone numbers and email addresses, duplicates and plausibility. Anything unclean goes on a review list instead of silently into the new system. You start with data that is better than before.
HC24 data bridge
A smooth transition instead of a big bang
The HC24 data bridge connects your Access database to the new CRM and pushes changes across continuously while the parallel phase runs. Both systems stay in sync — your team switches module by module, with no cut-over risk and no weekend heroics. Switch-off happens only once nobody needs the old database anymore.
Tailored in-house modules are not lost either: thanks to HC24 we port custom Access builds into the CRM world as extensions — the logic stays, only the foundation becomes modern.
Migration assistant
Tell us what lives in your Access database
Four quick questions about your setup. Your answers prefill the request — and we come to the free first consultation with a fitting migration proposal.
Your Access inventory — our migration proposal
Module: VBA under the microscope
We analyse each module individually — much is covered by standard tools, the rest is ported as an extension.
Module: reports become analyses
Your Access reports become one-click analyses — from data that is maintained anyway.
Module: connect invoicing cleanly
We review quotes and invoices in the first conversation: a fitting add-on or a link to your accounting.
Module: screens become CRM forms
We rebuild input screens in the CRM — plus mobile capture on the go, for example with GiContact.
Risk: knowledge monopoly
When nobody maintains it anymore, speed matters — the data bridge keeps operations stable while we migrate in order.
Your answers are not stored — they only prefill your request. The first consultation is free.
Frequently asked questions
What happens to our VBA modules?+
We analyse each module individually. Much is covered by standard tools — Outlook integration, telephony, reports. What remains, we rebuild as a tailored extension so no function is lost.
What replaces our old TAPI dialer?+
GiPhone — a SIP softphone that lives right in the CRM: start calls with one click on the contact, incoming calls open the record, every call lands in the history. No more TAPI drivers or legacy dialer helpers.
Is data lost during the move?+
No. We map every field, migrate in a test run first and compare the datasets. The old database stays untouched during the parallel phase — you can always look things up.
Can we keep using Access in the meantime?+
Yes, that is the normal case: your team keeps working in parallel until the CRM has taken over every task. Switch-off happens only on the agreed date.
What is the HC24 data bridge?+
Our transition layer between the old database and the CRM: it pushes changes into the new system continuously while the parallel phase runs. Instead of a cut-over migration, your team switches smoothly — switch-off happens only once nobody needs the old database anymore.
Does this also apply to FileMaker or other homegrown tools?+
Yes — FileMaker has its own page covering the specifics around layouts, scripts and FileMaker Go. We retire Excel collections and old vertical solutions the same way: inventory, field mapping, test migration, parallel phase.
What does replacing an Access database cost?+
That depends on the number of modules and fields. The first conversation costs nothing — after that you get a quote with a clear scope before any costs arise.
“
The goal is not to rebuild Access one to one — it is to move the workflows behind it into a system your team enjoys using.
HartCon.24 — your companion for CRM, hosting and software development.Let's talk.
Get a free initial consultation — we take your business to the next level.