User/Resource Fields: Users on synced projects are are automatically associated across the systems by their email address. Once the association is established, then the following fields are exchanged across the systems.
| Moovila | Autotask | Notes |
|
First Name |
First Name | Syncs from Autotask into Moovila |
| Last Name | Last Name | Syncs from Autotask into Moovila |
| Email Address | Email Address | Syncs from Autotask into Moovila |
| Title | Title | Syncs from Autotask into Moovila |
Project: Projects are associated across systems via their unique identifiers.
| Moovila | Autotask | Notes |
| Name | Name | |
| Description | Description | |
| Reference Number | Project Number | Syncs from Autotask into Moovila |
| Status | Status | Requires mapping |
| Start Date | Start Date | |
| Due Date | End Date | |
| Owner | Project Lead | |
| Customer | Account |
Project Phase:
| Moovila | Autotask | Notes |
| Name | Name | |
| Description | Description |
Task: Moovila and Autotask Tasks are bi-directionally synced across the systems.
| Moovila | Autotask | Notes |
| Name | Title | |
| Description | Description | |
| Reference Number | Task Number | |
| Status | Status | Requires mapping |
| Priority | Priority | Requires mapping |
| Task Owner | Primary Resource | |
| Default Work Type | Work Type | Department and Role will be set based on Resource/User default configuration |
| Work Estimate | Estimated (h) | |
| Start Date | Start Date | |
| Due Date | End Date |
Time: Moovila and Autotask Time are bi-directionally synced across the systems.
| Moovila | Autotask | Notes |
| Effective Date | Date Worked | |
| Clock In | Start Date/Time | |
| Clock Out | End Date/Time | |
| Total Time | Hours Worked | |
| Billable Hours | Hours to Bill | |
| Notes | Summary Notes | If a note is not provided in Moovila, "No notes provided in time entry from Moovila" will be the entry. |
| Billable/Non-Billable | Is Non-Billable | Billable/Not-Billable Status is based on the Work Type configuration in Autotask. |
| Work Type | Work Type | |
| User | Resource |
Project and Task Notes:
| Moovila | Autotask | Notes |
| Note | Note Body | |
| N/A | Title |
“Title” is required in Autotask. Notes created in Moovila will apply the following text for title:
|
| Note Category | Note Type | Requires mapping for default Note Type, as it cannot be blank in Autotask. |
| Note Visibility | Publish | |
| Creator | Resource |
Moovila Task Scheduled Event / Autotask Service Calls: Moovila and Autotask project-related schedule entries are bi-directionally synced across the systems. See below for considerations around this data mapping.
| Moovila | Autotask | Notes |
| Resource (User) | Resources | *Autotask can have multiple resources and tasks assigned to one service call. These can be created as individual schedule events in Moovila and tied to the single service call in Autotask. |
| Schedule Start Date | Start Date | |
| Schedule Start Time | Start Time | |
| Schedule Due Date | End Date | |
| Schedule Due Time | End Time | |
| Duration | Hours | |
| Status | Status | |
| Description | Description |
Considerations
- In Autotask, a single service call can be linked to multiple tickets and/or resources. When this occurs, Moovila creates individual schedule items for each associated ticket and/or resource.
- The Autotask integration automatically consolidates these items during updates to ensure that only one unified service call remains in Autotask.
Note: Because these items are consolidated, changes made in Moovila — such as updates to the appointment name or description, or scheduled time — will affect the corresponding master service call in Autotask, and therefore all associated tickets and resources upon the next sync back into Moovila. - The standard business rules will apply for who can be added to a service call (and added as a secondary resource on the task to be allowed service call association). For example, the user must be on the department that is associated to the task.
Comments
0 comments