MOCO Integration for Transferring Projects, Time Tracking, and Absences

💡 This interface is a paid add-on. If you'd like to use our MOCO integration, just reach out to us at sales@awork.com. We'd love to hear from you!

MOCO is agency software that lets you handle your accounting and many other helpful features without stress and paperwork.

We offer several integrations for MOCO:

  1. Free MOCO integration for invoices
  2. Paid MOCO integration for transferring projects and time tracking
  3. Free MOCO browser extension for Chrome and Firefox to log time directly in MOCO while you're working in awork

General Information

The MOCO integration is a paid add-on module that enables seamless transfer of projects, time entries, and absences between awork and MOCO. This keeps all relevant data centrally available and supports your workflow efficiently. In this article, you'll learn how to set up the integration and what features it offers.


What features does the integration offer?

Projects

  • Synchronize new projects from MOCO to awork
  • Use project templates from awork
  • Transfer existing projects from awork to MOCO

Time Tracking

  • Automatic transfer of all time entries, no manual follow-up needed
  • Option to start the transfer from a specific point in time
  • Ability to distinguish between billable and non-billable time

Absences

  • Only new or changed absences are synchronized from MOCO to awork
  • No synchronization in the other direction (awork to MOCO)

How does the integration work technically?

1. Project Creation:

  • The project is created in MOCO and tagged with "Sync to awork".
  • The interface automatically creates the project in awork. The following data is transferred:
    • Project number
    • Project name
    • Start and end date
    • Client (is created or selected and assigned to the project)
  • Project manager and project members are synchronized to awork by default.

2. Tasks from Service Items:

For each service item from the MOCO project, a task is created in the "MOCO" list in awork.

3. Time Tracking:

  • A time entry is created in awork on the linked project.
    • If the time was logged on a task that originated from a MOCO service item, the time is assigned directly.
    • If direct assignment isn't possible, the time entry is matched based on the activity name and the MOCO position name.
    • If no match is found, a new service item called "Unassigned Time Entry" is created in MOCO and the time is assigned there.
    • Subtasks are assigned to the same MOCO service item as the main task.
  • The user from MOCO and awork is matched via email address.
    Important: The email address in awork must be set as a business email under Account Settings (click on your profile picture in the top right) > Edit User > Contact. Admins can also update the email for other users under Users in the left navigation bar.
  • Information about whether the time is billable or non-billable is carried over.
  • Time entries can be changed or deleted in awork after the fact. These adjustments are also transferred to MOCO.


Time Tracking Modes: Task Lists vs. Tasks

There are two supported modes for synchronizing time tracking between MOCO and awork:

  1. Time tracking via task lists (recommended)
  2. Time tracking via tasks

Each mode determines how service items and logged time are mapped between the systems.

A separate task list is created in awork for each service item. Tasks are not automatically created. Users can manually create tasks or subtasks within the generated task lists.

  • Reusing existing task lists: If the project template already contains task lists with identical names, these existing task lists are reused and tasks are assigned to the matching existing lists instead of creating duplicates.
  • Time entry assignment: All time logged within the corresponding task list is assigned to the linked service item, including time on tasks and subtasks.
  • Assignment logic: MOCO service item = task list in awork. Time logged on tasks/subtasks = assignment to the corresponding service item.

This mode is recommended because it offers:

  • More flexibility in task organization
  • Better compatibility with project templates
  • Clearer project structures
  • Simpler manual task management

2. Time Tracking via Tasks

A list called "MOCO" is automatically created in awork. Within this list, a separate task is created for each MOCO service item.

  • Time entry assignment: Time logged directly on these created tasks is synchronized back to the corresponding service item. The assignment happens directly via the task created from the service item or via the linked awork activity.
  • Assignment logic: MOCO service item = task within the "MOCO" list in awork. Time logged on task or activity = transfer to the corresponding service item.

How do I set up the integration?

Step 1: Create an API Key in MOCO

  • In your MOCO account: Settings (gear icon in the top right) > Extensions > API and Webhooks
  • Create a new API key with:
    • A name (e.g., "awork")
    • Full access, unlimited validity
    • Copy the key and store it securely

2. Create Custom Fields in MOCO

To ensure the transfer works correctly, custom fields must be set up in MOCO:

  1. Go to Settings (gear icon in the top right) > Custom Fields.
  2. Create the following fields:
  • awork Project (Type: Link)
  • Sync to awork (Type: Yes/No)
  • awork Project Template (Type: Single Select). Add template names as described above.
  1. When creating each field, select Project in the second row.
  2. Pay attention to uppercase and lowercase letters.
  3. Save the fields.

3. Activate the Integration in awork

Now contact our support team and ask them to enable the MOCO interface in awork for you.

Send them the API key you just created and your MOCO subdomain. We need both to configure the interface.

Please let the team know how you'd like the following details configured:

  1. Synchronization of absences from MOCO to awork: Yes/No
  2. Time tracking via task lists or via tasks
  3. Time entries from a specific point in time onwards

4. First Test

  1. Create a project:
  • Create a new project in MOCO and enable the Sync to awork field.
  • Save the project.
  1. Check the transfer:
  • Verify in awork that the project was transferred correctly.

Additional Optional Integration Settings

The following optional settings can be configured:

  • Ignore non-plannable absences: Decide whether non-plannable MOCO absences should be excluded from synchronization
  • Disable MOCO-controlled updates of awork project data: Prevents changes from MOCO from overwriting existing project data in awork (including project budget and project description)
    • Or only disable updates to awork project descriptions: allows project data to continue syncing while preserving existing awork project descriptions to avoid text overwrites
  • Remove MOCO ID prefix from awork project names: ensures more consistent naming in your workspace ("Project Name" instead of "P1234 - Project Name")
  • Update project budget from planned durations: calculates the awork project budget based on the total planned durations of tasks and task lists
  • Disable project member updates during project updates
    • Or never transfer project members: completely disables synchronization of project members between MOCO and awork

Please let us know which options you'd like us to enable for your workspace.


Project Creation in awork with Templates

  1. Create a custom field: Go to Settings (gear icon in the top right) in MOCO and create a custom field named "awork Project Template" as type "Single Select".
  2. Add templates: Add the templates you want to use in MOCO/awork to the single select options. Important: Make sure there are no spaces before or after the comma.
  3. Use template: The selected template is automatically used for project creation in awork.

If you'd like no template to be preselected by default, or if users should be able to create a project completely without a template, then add a comma at the beginning, right before the project template names in the awork Project Template field.


Important Notes

  • User permissions in both systems:
    Check that user permissions are correctly set in both systems and that the user is assigned to the respective projects. This must be identical in awork and MOCO. In MOCO, the user needs full access to projects and must be added as a "person for time tracking" to the project.
  • Transfer existing MOCO projects to awork: If you want to create existing MOCO projects in awork, simply activate Sync to awork retroactively. The project will then be created in awork.
  • Custom subdomain: If you change your awork domain after activating the MOCO integration, please contact support so we can update the domain for the integration.
  • Transfer existing awork projects to MOCO:
    If you want to retroactively transfer existing awork projects to MOCO, create a MOCO project, add the corresponding link to the awork project, and then activate Sync to awork.

Project linking is only possible once. Already used awork project links cannot be inserted into another MOCO project. This will cause synchronization errors.


Canceling the MOCO Integration

You cannot cancel the MOCO integration yourself in awork. Please contact our support team at support@awork.com to do this.


Frequently Asked Questions (FAQ)

What does the integration cost?

We charge a flat rate of 50 euros per month for the integration. The minimum contract term and cancellation period for this add-on are based on your current plan's terms.

Is the task title in awork transferred to the time entry description in MOCO?

Yes, the task name can be transferred to the notes field of the time entry in MOCO. Just let our support team know when activating the integration if you'd like to use this feature. The feature can also be enabled later.

Can a task in awork be renamed or will time entries no longer be assigned afterwards?

Time entry assignment continues to work even if a task is renamed.

Are changes to time entries in awork also updated in MOCO?

Yes, duration and notes of a time entry are transferred to MOCO when you make changes in awork.

Will time entries be synchronized again from awork to MOCO if the time entries were already manually transferred to MOCO and the integration is activated afterwards?

Yes, the time entries would be transferred again, but you can define a point in time from which the transfer of time entries should begin. Inform our support team about this point in time when the interface is activated.

Is it possible for changes to projects in MOCO to be synchronized to awork even after the initial project creation?

Subsequent transfer occurs only for newly created service items and project members specified in MOCO. To trigger synchronization, the project name must be edited (for example, by adding a space at the end).

If time entries are edited or deleted in MOCO, are they also edited or deleted in awork?

If a time entry is edited or deleted in MOCO, no synchronization occurs with awork. Conversely, if you change or delete a time entry in awork, it is updated or deleted in MOCO as well.

If a project is deleted in MOCO, is the project in awork also deleted?

No, deleting a project in MOCO has no effect on the project in awork. The project in awork will not be deleted.

Can time entries be synchronized from MOCO to awork?

Time entries are only transferred from awork to MOCO, not the other way around.

Is the budget of tasks created in MOCO also transferred to awork?

The budget is not transferred directly from MOCO to awork. MOCO uses a monetary budget, while awork uses a time-based budget. The planned effort of a task in awork, however, is based on the budget of a MOCO service item and the hourly rate stored in MOCO. (Formula: MOCO budget / MOCO hourly rate = awork planned effort)

If no budget is set for the service item, the integration uses the budget of the MOCO project.

Is the service item description from MOCO transferred to the description field in awork?

Yes, that's possible. The description should be transferred here.

Can the transfer of project members from MOCO to awork be disabled?

Yes, project member transfer can be disabled either only for existing projects or completely when creating new projects. Please contact support so we can configure the interface accordingly.

I already created a project in MOCO that was transferred to awork. Can I create a new awork project from this project?

The projects are automatically linked. If you want to remove the link, you can deactivate the sync checkbox in MOCO.

If you want to create a new awork project from the MOCO project, proceed as follows:

  • Edit the project in MOCO and delete the awork link
  • In the link field, enter the following text: https://recreate
  • Once you save the project in MOCO, a new project will be created in awork

No, an awork project can only be linked to one MOCO project. For example, if a MOCO project is archived, the awork project cannot be linked to another MOCO project. The original link remains.

Last updated HappySupportPowered by happysupport.ai
© 2026 HappySupport. All rights reserved.