MOCO Integration for Transferring Projects, Time Tracking, and Absences

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

MOCO is agency management software that lets you handle your accounting and many other useful 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 work in awork

---

General Information

The MOCO integration is a paid add-on module that enables seamless transfer of projects, time tracking, 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 provide?

Projects

• Sync 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 synced from MOCO to awork
• No sync 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 (will be created or selected and assigned to the project)
• Project manager and project members are synced to awork by default.

2. Tasks from service items:

For each service item from the MOCO project, a task is created in the "MOCO" task 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 came from a MOCO service item, the time is assigned directly.
  • If no direct assignment is possible, the time entry is matched based on the activity name and the MOCO service item name.
  • If there's no match, a new MOCO service item called "Unassigned time entry" is created 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 stored 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 User in the left navigation bar.
• Information about billable or non-billable time is transferred.
• Time entries can be changed or deleted in awork later. These adjustments are also transferred to MOCO.

---

Time Tracking Modes: Task Lists vs. Tasks

There are two supported modes for syncing 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 matched between the systems.

1. Time Tracking via Task Lists (Recommended)

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, those existing task lists are reused and tasks are assigned to the matching existing lists, instead of creating duplicate lists.
• 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. Logged time on tasks/subtasks = assignment to the corresponding service item.

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 generated tasks is synced back to the corresponding service item. Assignment happens directly through the task created from the service item or through 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:
  • Name (e.g., "awork")
  • Full access, unlimited validity
  • Copy the key and store it securely

2. Create custom fields in MOCO

To make the transfer work 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.

3. When creating them, select Project in the second row for each field.
4. Pay attention to uppercase and lowercase letters.
5. 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.

4. First test

1. Create a project:

• Create a new project in MOCO and enable the Sync to awork field.
• Save the project.

2. Check the transfer:

• Check in awork whether the project was transferred correctly.

---

Additional Optional Integration Settings

The following optional settings can be configured:

Please let us know which options we should enable for your workspace.

---

Project Creation in awork Using Templates

1. Create a custom field: In MOCO settings (gear icon in the top right), create a custom field called "awork Project Template" with 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 the template: The selected template will be automatically used for project creation in awork.

---

Important Notes

• User permissions in both systems:
  Check both systems to make sure user permissions are set correctly and 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 "Person for time tracking" in the project.
• Transferring existing MOCO projects to awork: If you want to create existing MOCO projects in awork, simply activate Sync to awork afterwards. 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.
• Transferring existing awork projects to MOCO:
  If you want to transfer existing awork projects to MOCO later, create a MOCO project, add the corresponding link of the awork project, and then activate Sync to awork.

---

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 duration and notice period for this add-on are based on the terms of your current plan.

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

Yes, the task name can be transferred to the note field of the time entry in MOCO. Just let our support team know when you activate the integration that you want to use this feature. The feature can also be activated later.

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

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 changes are made in awork.

Will time entries be synced again from awork to MOCO if they 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 time entries should be transferred. 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 synced to awork after the initial project creation?

A re-transfer only happens for newly created services and the project members defined in MOCO. To do this, the project name must be edited (e.g., by adding a space at the end) to trigger the sync.

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 sync to awork occurs. In the other direction, if you change or delete a time entry in awork, it will be updated or deleted in MOCO as well.

If a project is deleted in MOCO, will the project in awork also be 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 synced from MOCO to awork?

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

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

Budget is not directly transferred from MOCO to awork. MOCO uses a monetary budget, while awork uses a time-based budget. The planned effort of a task in awork 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, the integration uses the MOCO project budget.

Is the description of the service item 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, the transfer of project members 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've 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 disable 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
• When you save the project in MOCO, a new project will be created in awork

Can I change the link later and link an awork project to a different MOCO project?

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.

Who is responsible for the MOCO integration?

awork is responsible for the integration. Contact the awork support team if you have any questions.