Skip to content

How the sync works

Once a project is linked, there is nothing to do: the sync runs on its own and the two sides follow each other. This page explains what is copied, when, and what happens when both sides change.

When a sync runs

Trigger What happens
the schedule (every 15 minutes by default, per project in Settings) the project is read and its changes are written
Sync now on the project's row or page the same, immediately; a toast reports that the project syncs within a minute
an Exact event when hours change status in Exact, the next run is brought forward

OpenProject is read on the schedule: the app does not need a webhook in your OpenProject, so nothing has to be installed or opened up on your side. A run reads in pages and continues where it stopped, so a big first run takes several turns. While one run of a project is busy, another request for the same project waits.

What is copied

Time entries → draft hour lines

Every time entry on a work package or on the project itself (within the type filter and the sync window) is summed per person, per work package and per day:

  • one line is created or updated in Exact as a Draft, on the linked project, the administration and hour type from the link;
  • the day is counted in the link's time zone;
  • negative entries (a correction in OpenProject) net out against the same person/work package/day; when the sum drops to zero or below, the line is deleted again, but only while it is still a Draft;
  • a line that was deleted in Exact is never re-created;
  • the first run takes everything from Sync time logged from; every later run covers the last 45 days, so corrections still come through.

The lines are drafts on purpose: the person who books the hours in Exact can still adjust them, and nothing is submitted or posted by the sync.

Work packages and versions → WBS

When the WBS mode is Work packages → activities:

  • every in-scope work package becomes a WBS activity on the linked Exact project; the parent/child hierarchy becomes the WBS structure, and dates, estimated hours and the closed status are mapped;
  • with Versions → deliverables, versions become WBS deliverables and their work packages the activities below them;
  • WBS lines are never deleted in Exact, because hours may be booked on them: delete them there when a project is finished;
  • a work package renamed in OpenProject renames its WBS line on the next run.

Exact → OpenProject: the status comments

When status comments are on and the token's user may comment:

State of the lines in Exact Comment on the work package
any line rejected Exact Online rejected 2 hour lines. Correct them in Exact and submit again.
every line final (approved) 3 hour lines approved in Exact Online.

A comment is posted when the status of a work package changes, not on every run. Draft-only work packages get no comment. Hours are never copied back into OpenProject: only the status is reported.

People

OpenProject users are matched to Exact employees per OpenProject connection and per administration:

  • a user whose e-mail address equals an employee's business e-mail is matched automatically;
  • everyone else appears under People as unmapped until an employee is chosen; while unmapped, the user's hours are skipped (they are not booked on someone else, and not lost: they are picked up once the user is mapped);
  • Ignore deliberately excludes a user (a service account, for example).

People

The People page: OpenProject users matched to their Exact employee, with search and the unmapped-only filter

What Where
the list People, one row per OpenProject user, grouped per administration when there is more than one
search and unmapped only above the list; unmapped only is on by default while unmapped users exist
a suggested employee a name or e-mail close to an Exact employee is offered as Suggested; Accept confirms it, Accept all suggestions does it for everyone
choosing the select per row saves immediately (a tick and a toast); Ignore excludes the user
from a run a run summary that mentions unmapped users links straight to People filtered on them

Conflicts

The sync only writes hour lines while they are Draft (or Rejected). When OpenProject says a line should change but Exact already has it Submitted or Approved, the difference is a conflict:

  • the run stops at the line and records the difference;
  • the project's status chip shows Conflicts: n, and the Overview page counts them;
  • on the project's page, the Conflicts tab lists each one: the date, the person and what changed in OpenProject after the hours were submitted or approved;
  • resolve it in Exact (change or delete the line, or reject it so the sync may update it): the next run re-reads both sides and the conflict clears when they agree again.

The sync never silently overwrites an approved line, and never books an hour that a person removed.

What is not synced

  • time entries outside the sync window on the first run (older than Sync time logged from);
  • hours of unmapped OpenProject users (skipped, and listed under People);
  • budgets, costs and attachments: OpenProject's budget model and Exact's project budget are not mapped;
  • anything in Exact besides the linked project's time lines and WBS (no posting, no invoicing, no projects created outside the wizard);
  • work packages outside the type filter.