Excel-SQL Sync Automation

$250-750 USD

Posted 1 minute ago

•

Ends in 6 days

$250-750 USD

Paid on delivery

I need a small, reliable system that lets me keep a few chosen sheets from my master Excel workbook fully in sync with SQL Server 2019. A single button click in Excel should: • push any new or updated rows to SQL • pull any changes from SQL back into the same sheets Conflict handling must always keep the newest version of a record. To make that possible, add a hidden date-time stamp whenever a row changes so the macro can decide which side is fresher. Behind the scenes, use MERGE/UPSERT logic to preserve primary keys, treat NULLs, dates, and numeric types correctly, and avoid duplicates. What I expect delivered • a macro-enabled workbook (.xlsm) with clean, commented VBA and Power Query steps • SQL scripts that create or adjust the target tables and indexes • an error log that lists any rows that fail to sync and the reason • a concise hand-over PDF so my analyst can maintain or tweak the solution later You may work in Windows 11 and Office 365; those match my environment. A first working build within a couple of days would be ideal so we can test quickly.

Project ID: 40806022

About the project

29 proposals

Open for bidding

Remote project

Active 3 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

29 freelancers are bidding on average $369 USD for this job

User Avatar
Flag of UKRAINE

Hello, I have experience with Excel automation, VBA, SQL and C#, and can build a reliable two-way synchronization between your selected Excel sheets and SQL Server 2019. I would implement timestamp-based change tracking, SQL MERGE/UPSERT operations, and conflict resolution to ensure the newest record wins without creating duplicates. Special attention will be given to data types, NULL values, primary keys, and error logging. Deliverables will include the commented VBA workbook, SQL scripts, Power Query setup, error log, and a concise PDF handover guide. I suggest starting with one or two sheets to validate the synchronization and conflict-handling logic before extending it to the remaining sheets.

User Avatar
Flag of PAKISTAN

Your Excel button needs to reconcile changes in both directions without overwriting a newer edit or creating duplicate records. I’ll add a hidden UTC edit timestamp to the selected sheets, track SQL-side changes with a trigger, and compare timestamps by primary key before applying updates. VBA will handle the button and writes; Power Query will handle reads. The SQL scripts will use a transaction-safe UPSERT with type-aware handling for NULLs, dates, and numbers, plus indexes to support matching. Failed rows will go into an error log with their keys and reasons, while successful rows remain available to sync. I’ll deliver the commented .xlsm, SQL scripts, and a short PDF explaining how to add a sheet or adjust column mappings. The first build can focus on one representative sheet so you can test conflict handling before it is extended to the others. Accurate “newest wins” decisions depend on the Excel PC and SQL Server clocks being synchronized. Could you share a sample workbook and the target table schemas, including each sheet’s primary-key column?

User Avatar
Flag of PAKISTAN

Two-way Excel/SQL sync needs reliable change tracking to prevent newer records from being overwritten. I'd use VBA with ADO for SQL Server 2019 UPSERT operations, Power Query for refresh, and hidden timestamps for conflict resolution. The workbook will include a one-click sync, primary-key protection, type-safe handling, and row-level error logs. I'll provide SQL scripts, an .xlsm file, and a handover PDF. A first test build within 2 days is feasible. How many sheets and columns need syncing?

User Avatar
Flag of TANZANIA, UNITED REPUBLIC OF

Hello, Your sheets can stay the place you actually type, and SQL Server can stay the copy everyone else trusts. I would drop a hidden last-changed time on each synced sheet. Any edit refreshes that stamp, so one button can see which side is newer and keep that version. Older data never writes over a fresher row. Push goes through a small staging table first. A MERGE then updates matching keys and inserts new ones, with blanks, dates, and numbers treated the way SQL expects, so keys stay unique. Pull uses Power Query to bring SQL changes back into the same sheets, and only swaps a row when SQL is the fresher one. Rows that fail land in a simple log: which row, and the reason, like a bad date, a missing key, or a type that will not fit. You get the macro workbook with commented VBA, SQL scripts for the tables and indexes, and a short PDF your analyst can follow when a column needs a tweak later. A first build in a couple of days on Windows 11 and Office 365 is realistic, then we test it on your real sheets and lock the rules. Send a sample workbook and the key columns and I can start.

User Avatar
Flag of TURKEY

Hi there, I understand you need a reliable system to keep specific sheets from your Excel workbook in sync with SQL Server 2019. I propose creating a macro-enabled workbook that implements a seamless two-way sync using VBA and Power Query. I would ensure that the merging logic is correctly handled with the newest record version prioritized, and I'll include hidden timestamps for tracking updates efficiently. In terms of deliverables, I will provide the macros with comprehensive comments for clarity, the necessary SQL scripts for table adjustments, and an error log to help diagnose any sync issues. A concise hand-over PDF will also be included to assist your analyst with future maintenance. I'm ready to start working on this as soon as possible and can deliver a working build within two days for your testing. Regards, Ali

User Avatar
Flag of MALAYSIA

Keeping a few sheets of a master Excel workbook in sync with SQL without manual exports is a classic VBA plus scheduled task job. I would build a macro that pushes only the chosen ranges to your SQL tables on save or on a timer, with logging so you can see what synced and when. Can start today, working version in 4 days. These numbers are based on the post as written, we will refine them once we talk through the real scope. Want me to send a quick plan?

User Avatar
Flag of UNITED STATES

Hi there, Keeping selected Excel sheets and SQL Server 2019 synchronized requires more than a basic import/export macro: the button must resolve conflicts by row timestamp, preserve keys, and handle NULLs, dates, numeric types, and failures reliably. I have strong hands-on experience with Automation and have solved similar problems involving Excel VBA workflows, SQL Server data synchronization, and reliable upsert processing. My approach would be to: * Review the workbook structure, selected sheets, keys, and target SQL schema. * Identify the root cause of possible sync conflicts and determine what can be reused versus what needs to be changed. * Implement a clean, maintainable solution using VBA, Power Query, and SQL Server MERGE/UPSERT logic. * Test edge cases, reliability, performance, security, and integration behavior, including NULL values, duplicate prevention, and failed-row logging. * Deploy or integrate the fix without disrupting the existing workbook workflow. The hidden modified timestamp must be updated consistently on every local edit and compared against SQL timestamps; otherwise, a MERGE can silently overwrite newer data. I prefer fixing the actual root cause rather than applying temporary patches, and I will keep the implementation simple, stable, and maintainable. I can start by reviewing the workbook, sheet keys, target schema, and current sync setup, then deliver a first working build for testing within a couple of days. Best regards, Ian

User Avatar
Flag of UKRAINE

Hello, The key challenge here is not simply moving Excel rows into SQL Server, it is making two-way synchronization deterministic when both sides change, while preserving keys, NULLs, dates, numeric types, and avoiding duplicates. I would implement a button-driven VBA workflow with hidden row timestamps, SQL MERGE/UPSERT logic, and explicit newest-version conflict resolution. I have practical experience with automation systems, third-party integrations, Node.js, Python, and database-backed workflows; for this build, I will focus directly on clean commented VBA, Power Query steps, SQL scripts, row-level error logging, and a concise handover PDF. I can deliver a first working build within 2-3 days and complete testing and documentation within 5 days. Best regards, Bohdan

User Avatar
Flag of THAILAND

I’ve built Excel-to-SQL Server automation using VBA and stored procedures, including timestamp-based row synchronization and audit logging. For this project, the key is using a hidden LastModified column on both sides because it gives the sync a clear, repeatable rule for resolving conflicts. I’ll deliver an .xlsm workbook with a single sync button, commented VBA, and Power Query steps for the selected sheets. I’ll create SQL Server 2019 table, index, and MERGE/UPSERT scripts that preserve primary keys and correctly handle NULLs, dates, and numeric values. Failed rows will be written to an error log with the SQL or validation reason. I’ll verify inserts, updates, conflicts, and duplicate prevention before handover, then provide a concise maintenance PDF. Thanks, Kittipong

User Avatar
Flag of BANGLADESH

Hi, With 7+ years in software development, I can build bidirectional Excel–SQL Server 2019 synchronization using VBA, Power Query, timestamps, and MERGE/UPSERT logic. I'll include conflict resolution, error logging, SQL scripts, and documentation. A testable build within 2–3 days is feasible. How many sheets and approximate rows require synchronization? Let’s discuss in chat to proceed further.

User Avatar
Flag of PAKISTAN

Dear Client, FinTax Global Solution LLC is a team of CA, ACCA, and CPA professionals with 8 years of experience, including experience in Big Four firms. Our team has strong expertise in advanced Excel, VBA automation, SQL-based data management, Power Query, and financial data processing. We can develop a reliable Excel-to-SQL Server synchronization solution with a one-click VBA button to push new and updated records to SQL Server 2019 and retrieve changes back into the selected worksheets. We can implement timestamp-based conflict resolution, SQL MERGE/UPSERT logic, primary-key preservation, duplicate prevention, and accurate handling of NULL values, dates, and numeric data types. We will also provide commented VBA code, Power Query steps, SQL scripts, error logging, and a concise PDF handover guide to ensure the solution is maintainable and easy to use. **A couple of questions:** 1. How many worksheets need synchronization, and do they already have unique primary keys or record IDs? 2. Should synchronization run automatically based on the latest timestamp for each individual record, including when changes occur on both Excel and SQL Server? I would be happy to develop the first working build within your proposed timeline and provide a reliable solution for testing and long-term maintenance. Best regards, FinTax Global Solution LLC

User Avatar
Flag of SOUTH AFRICA

Hi, a hidden UTC timestamp per row plus a staging-table MERGE in SQL Server 2019 is the cleanest way to make your one-button Excel sync keep the newest record, with no duplicates and NULLs, dates and numerics typed correctly. Approach: VBA bulk-loads the changed rows into a staging table, then a stored procedure runs MERGE on the primary key and compares timestamps in both directions. Newer SQL rows come back into the sheet in one array write. Failed rows land in an error log with the reason. You receive the .xlsm, the table and index script, and a short PDF for your analyst. First working build in 24 to 48 hours, not the 5 to 9 days others quote. Send a sample sheet and I will run a test pass in chat so you can verify the sync behaviour before funding Milestone 1. Which column is your primary key, and can two people edit the same row at once? Best regards, Tumisang

User Avatar
Flag of INDONESIA

Hi there, I appreciate the clarity of your project requirements for automating two-way sync between selected Excel sheets and SQL Server 2019. As an experienced freelancer specializing in Excel VBA, SQL Server integration, and automation solutions, I understand the critical importance of maintaining data integrity and ensuring seamless, reliable sync processes. Your need for a macro-enabled Excel workbook that can, with a single click, both push updates to SQL and pull any changes back—while resolving conflicts based on the latest modification timestamp—is very much in my wheelhouse. I have successfully delivered similar automation solutions where careful handling of primary keys, data types (NULLs, dates, numbers), and robust conflict resolution is essential. My approach will be to design a well-documented VBA macro that tracks changes via hidden datetime stamps, leverages Power Query for efficient data handling, and uses SQL MERGE/UPSERT logic to accurately synchronize records. Error handling will be thorough, with a detailed log for any rows that fail to sync and clear reasons provided. I will provide SQL scripts to create or adjust your target tables and indexes, ensuring your SQL Server structure fully supports the sync logic. Finally, I will deliver a concise, user-friendly PDF guide so your analyst can maintain or enhance the solution with confidence. Looking forward to collaborating and ensuring your workflow is both efficient and reliable. Best Regards

User Avatar
Flag of PAKISTAN

Hi, Keeping the newest version of each record across Excel and SQL Server 2019 is the tricky part here, so I would stamp every changed row with a hidden timestamp and let a MERGE decide which side wins. Primary keys, NULLs and date/numeric types would be handled explicitly so nothing gets duplicated, and failed rows would go to a clear error log. Which key columns identify a record in your sheets today? https://www.freelancer.com/u/alyan056 Happy to chat about the details whenever suits you. Alyan

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

把喜欢的内容,留在你的新标签页。

打开我的订阅