Run a sync and what happens next
You will want this after setting a configuration up, after changing a mapping, and any time something in the accounting system changed and you do not want to wait.
- A walkthrough video, then the four steps
- What a successful run reports, and where it shows up
- Why the row still says "Last sync: Never" afterwards
- What happens to records that are already there
01 · Video
Feature walkthrough
02 · Why
When would I run one by hand?
After setting a configuration up, after changing a mapping, and any time something in the accounting system changed and you do not want to wait.
03 · How
Run one
- Go to Settings → Integrations and press
Sync Mappingson your connection. - Press the circular-arrow icon on the configuration you want.
- Wait a few seconds.
- To run every configuration on that connection, press
Sync Allinstead.
04 · Expected result
The configuration reports what it did, on the row itself — for example Synced 29 records.
In the destination table, the records appear or update, and their INTEGRATION column shows Synced — see What a record's sync state means. The run is also listed on the table's Integration Logs tab and in the connection's Sync Status.
05 · Troubleshooting
Nothing happened and no count appeared
Check the pull switch is on, and that the connection is Connected rather than Degraded.
Fewer records than expected
A sync only writes fields you mapped, and it skips records it considers unchanged.
06 · Notes
Running a sync updates existing records rather than duplicating them
In our testing, syncing 29 QuickBooks customers into a table of 71 records left it at 71 — the matching records were updated in place.
Records only change where you mapped a field
Columns you left on skip keep whatever they had, which is why freshly synced records often show Not set in most columns.
07 · FAQ
Common questions
Seconds for a few dozen records.
Sync All runs every configuration on the connection one after another.
For mapped fields, yes — the accounting system is treated as the source. Leave a field unmapped if Merchaint should own it.