Database synchronization

Good day, Yulia!

The task is clear - two-way synchronization between Microsoft Access and CRM SalesDrive based on status changes.

I will implement it through a Python script:
- When the status in the SalesDrive funnel changes (webhook or polling) - update the record in Access via ODBC
- When the status in Access changes - send the update to SalesDrive via REST API
- Protection against cyclical synchronization (change source flag)
- Logging of all operations
…
Please clarify: Is Access a local file or on a shared server? Is synchronization needed in real-time or on a schedule (every N minutes)?

I am ready to discuss the details and start.

Show original

Translate

Good day, Yulia.

I propose an approach to synchronization:

1. First, I will analyze the structures of both databases (Microsoft Access and CRM SalesDrive), identify key fields and triggers for status changes.
2. Next, I will implement data transfer from CRM to Access via API or direct SQL export.
3. Then — the reverse flow from Access to CRM. I will use ETL processes to ensure integrity and logging.
4. Finally - testing data integrity and error handling.
5. Implementation and final configuration of ETL processes.
… 6. Documentation and handover.

PM: Source code and documentation included.

Show original

Translate

Hello! The task is absolutely clear, but it has one important architectural feature that I understand well: Microsoft Access is a local database, so a direct query from the cloud CRM SalesDrive cannot be sent there. To implement this two-way synchronization safely and reliably, I will develop a lightweight Python script (integration bridge) that will run on your computer or server where the database is physically located. In the first stage, the script will receive a signal about the change in the funnel status from SalesDrive via the API and will write the data directly into the Access table through the ODBC driver. In the second stage, the system will regularly monitor the local database for changes and automatically send the updated statuses back to the CRM. I have experience writing such integrations, so the code will be clean, stable, and wrapped in a convenient executable file (.exe) to ensure everything runs in the background without your intervention. Please write in private messages, and we will discuss the technical details of your database!

Show original

Translate

Understood — a bidirectional bridge Access ↔ SalesDrive for changing funnel status: the status changed in CRM — arrived in Access, and vice versa. SalesDrive provides this via API (webhooks for deal changes + REST for reverse writing), Access is connected through ODBC or a script connector. The most important thing here is not to create a synchronization loop: a record coming from CRM should not immediately trigger a reverse update, so I maintain status mapping and a change source flag plus a log. Questions: 1) Is Access a local .accdb on one machine or on a shared resource/SQL backend, and is there external access to it? 2) Is real-time synchronization (via webhook) needed or is polling every few minutes sufficient?

Show original

Translate

Good day! I can implement two-way synchronization between MS Access and SalesDrive via Python.
Stage 1: when the status of the funnel changes in SalesDrive — the record in Access is automatically updated.

Stage 2: when the status in Access changes — the data is sent back to SalesDrive via API.
I can implement it as a separate script or a background service with logging. Cost: 2500 UAH. Timeline: 3–4 days.
I am ready to discuss the details.

Show original

Translate

We already have a nearly ready similar solution for synchronizing CRM, statuses, and internal databases, which can be quickly adapted for SalesDrive and Microsoft Access. ))

The estimated first working stage is from 25,000 UAH and 7-10 working days.

We can do the exchange via the SalesDrive API, a separate synchronization module, an error log, and rules to ensure that statuses are not accidentally overwritten.

Look, here’s the nuance - we need to determine who is the main data source for each status, otherwise, bidirectional synchronization can create a fun little swamp, and we are supposed to be engineers, not shamans =)

> Please clarify, is Microsoft Access currently working as a local file or as a database on a shared server?
… > Which specific statuses need to be transmitted in the first and second stages?

Similar cases:
> https://business.ingello.com/forma-crm - CRM and business logic for operational processes
> https://business.ingello.com/platforma - corporate platform with roles, data, and integrations
> https://systems-fl.ingello.com/ua - our profile on systems, automation, and AI solutions

We can keep it simple - first, we will create a stable one-way exchange of CRM in Access, then we will add reverse transmission and conflict rules.

Show original

Translate

Good day! I have reviewed the task and am ready to start.

Experience:
• 4 years in Frontend and Backend development
• 2 years of commercial experience in product and blockchain
• Working with production code and real financial scenarios

Some of my projects:

… https://contentbuilder.ai/ - a commercial project from the USA, where I worked as a full-stack developer and implemented most of the functionality

https://freelancehunt.com/showcase/work/procasino/2025898.html

https://freelancehunt.com/showcase/work/bionrgg/2025897.html

Show original

Translate

Feel free to contact me, I will do it.

Show original

Translate

Hello! I have experience working with MS Access. I offer quality and fast work. Write to me.

Show original

Translate

Good day. I understand the task: two-way synchronization between Microsoft Access and CRM SalesDrive. In the first stage, data goes from CRM to Access when the funnel status changes, and in the second stage, it goes back from Access to CRM when the status changes in the program.

SalesDrive has an API, so synchronization on its side is done through it: we catch the change in deal status and update the corresponding record in Access, and vice versa, when there is a change in Access, we push the status update to CRM via the API. The key here is to carefully match records on both sides by a unique key and avoid creating a loop in synchronization, where an update from one side should not immediately trigger a reverse update. I will incorporate this logic from the start.

To assess more accurately: is your Access a local file or on a shared server, and how would you prefer to run the synchronization, on a schedule every N minutes or by event? And is there access to the SalesDrive API? After this, I will return with an exact estimate.

Show original

Translate

Hello! I have relevant experience with similar tasks, and I can help with your project. I can quickly familiarize myself with the requirements, propose the best solution, and execute the work carefully. I am ready to discuss the details and get started.

Show original

Translate