Skip to main content

Integrate Autotask with Partner Center

Connect your Datto Autotask PSA account with Vendasta to automatically sync company and contact records in both directions. When a record changes in Autotask, it appears in Vendasta within seconds — and vice versa. No Zapier. No manual data entry. No copy-pasting between systems.

This integration keeps your customer data aligned across both platforms so your team always works with current information.

Who can use it

Both Partners and their SMB clients. Partners manage the connection in Partner Center, while SMBs benefit from synced data inside Business App.

What gets synced

DataAutotask to PlatformPlatform to Autotask
Companies (clients)Auto-syncedAuto-synced (when enabled)
ContactsAuto-syncedAuto-synced (when enabled)

Before you begin — Autotask permissions

Before connecting, your Autotask account must be set up with the correct permissions. Without these, the connection may not work, and sync will fail silently.

You will need:

  • An active Vendasta account
  • An Autotask PSA account
  • Your Autotask API user's User Name and Secret (API key)
How to get API credentials

In Autotask, go to AdminResources (Human Resources)API User. Create a dedicated API-only user, selecting the integration vendor during creation.

Step 1 — Create a Security Level in Autotask

Creating a dedicated security level gives the integration a clean, controlled permission set.

  1. Sign in to Autotask.
  2. Go to AdminAccount Settings and UsersSecuritySecurity Levels.
  3. Click Create New and choose Clone an existing security level.
  4. Select Api User (System) as the template.
  5. Name it Vendasta API Access.
  6. Save.

Step 2 — Enable webhooks on the Security Level

Webhooks allow Autotask to notify Vendasta about changes in real time.

  1. Open the security level you created (Vendasta API Access).
  2. Go to the Other Settings tab.
  3. Find the Webhooks section.
  4. Set webhooks to Enabled.
  5. Set the maximum number of webhooks to at least 5 (the integration creates webhooks for Company and Contact events — create, update, and delete).
  6. Save.
warning

If webhooks are not enabled, the connection will appear as "Connected" in Vendasta, but changes in Autotask will not be synced back to Vendasta. This is the most common cause of "sync not working" reports.

Step 3 — Enable Company and Contact permissions

  1. In the same security level, go to the Companies tab.
  2. Enable Read and Write access.
  3. Go to the Contacts tab.
  4. Enable Read and Write access.
  5. Save.

Step 4 — Create an API User

The integration connects with a dedicated API user, not a personal login.

  1. In Autotask, go to AdminResources (Human Resources)API User.
  2. Click Create New.
  3. Fill in basic details like Name, Email.
  4. Go to the Security tab. Assign the Vendasta API Access security level (created in Step 1).
  5. In the API Tracking Identifier section, choose Integration Vendor and select the vendor.
  6. Save the user.
  7. Record the Username and Secret — you will need these in the next section.
warning

Store the API username and secret in your organization's approved password manager. Do not share them in email or chat.

Do you already have records in Vendasta?

Before connecting, answer this question: Do you already have companies and contacts in Vendasta CRM that also exist in Autotask?

Your situationWhat to do
No existing records in VendastaUse CRM Bulk Import to bring your existing Autotask companies and contacts into Vendasta, then connect. The integration handles real-time sync from that point forward.
Yes — records exist in both systemsYou must import Autotask IDs first to prevent duplicates. Follow the Bulk Import section below BEFORE connecting.
Already connected and seeing duplicatesFollow the Recovery section at the bottom of this page.

Bulk import — preventing duplicate records

If your Vendasta CRM already has companies and contacts that also exist in Autotask, you must link them with Autotask IDs before connecting. Without this, the sync creates duplicate records as records change in Autotask.

warning

Do this BEFORE connecting Autotask. Order matters — import companies first, then contacts.

Step 1 — Get your Autotask IDs

In Autotask, open each company or contact. The ID is visible in the URL bar or in the record detail panel.

Step 2 — Prepare your company CSV

Create a CSV file with the columns below. The external_id column is critical — it links the Vendasta record to the Autotask record.

The format must be exactly autotask:{id} with no spaces.

Company NameCompany WebsitePhone numberStreet address line 1City/localityState/province/regionZip/postal codeCountryExternal ID
Marqt Administratiewww.example.com856576871032 8th Street EastSaskatoonSKS7H 0S2CAautotask:30684201
Albany Apple Storewww.albanyapple.com55501234123 Main StAlbanyNY12207USautotask:29683562

Step 3 — Prepare your contacts CSV

Create a CSV file for contacts following the same format, with autotask:{id} as the external_id.

First nameLast namePhone numberEmailStreet address line 1City/localityState/province/regionZip/postal codeCountryExternal ID
JaneSmith5550100jane.smith@example.com1032 8th Street EastSaskatoonSKS7H 0S2CAautotask:30684161
SnehaIyer4353 4545sneha.iyer@example.com1 Grand Southern Trunk RoadChennaiTamil Nadu600016Indiaautotask:30686245

Step 4 — Import companies first

  1. Go to Partner CenterCRMCompaniesImport.
CRM Companies list with the Import button in the top right
  1. Upload your company CSV.
  2. On the mapping screen, make sure the external_id column is mapped to the External ID field.
Company CSV field mapping with External ID mapped
  1. Complete the import.

Step 5 — Import contacts

  1. Go to CRMContactsImport.
CRM Contacts list with the Import button in the top right
  1. Upload your contacts CSV.
  2. Map the fields — contacts will be associated with companies by company name.
Contact CSV field mapping
  1. Complete the import.

Step 6 — Verify

Open a few records in Vendasta CRM. Confirm the external_id field is populated with the autotask:{id} value.

Step 7 — Now, connect Autotask

Proceed to the next section. When the sync runs, it matches records by external_id — no duplicates.

warning

If you skip this step and connect first, the sync will create duplicate records for every company and contact. See the Recovery section at the bottom of this page if this has already happened.

Setting up the Autotask Integration

With your Autotask permissions configured and bulk import complete (if needed), you are ready to connect.

Step 1 — Open Integrations

From Partner Center, click AdministrationIntegrations. You can also access this from MarketplaceIntegrations.

Partner Center Administration page with the Integrations link under Advanced

Step 2 — Find the Autotask card

On the Integrations page, locate the Autotask card. Click Connect.

Autotask integration card on the Integrations page

Step 3 — Enter your credentials and choose sync settings

The Connect Autotask dialog appears. Both credential fields are required:

FieldWhat to enterWhere to find it
User NameThe username of your Autotask API userAutotask → Admin → API User (the ApiUser resource)
SecretThe API key associated with that userSame location — generated when the API user was created

The same dialog also contains two sync checkboxes. Both are selected by default — set them before you connect:

SettingWhat it doesRecommended
Sync back to AutotaskWhen an Autotask customer's details are updated in Vendasta, the change is reflected in AutotaskLeave selected for two-way sync
Set as Primary CRMDesignates Autotask as the primary system to receive newly created contacts from the platform. Changes made in Autotask also sync back into the platformLeave selected if Autotask is your main system

Click Add Connection.

Connect Autotask dialog with User Name and Secret fields and the two sync checkboxes
warning

If you see a 500 error at this step, your credentials are incorrect, or your API user is disabled. Go back to Autotask Admin and verify the username, secret, and that the user is active. Do not retry with the same credentials — it will fail again.

Step 4 — Connection confirmed

If your credentials are valid, the Autotask page shows a green Connected badge, along with Account details listing who connected the integration and when. A Disconnect button replaces Connect.

Autotask integration page showing a green Connected badge, Account details, and a Disconnect button

Step 5 — Review or change your settings

Your credentials and sync settings stay editable after connecting. On the Autotask page, scroll to SettingsIntegrated Service Fields to update the User Name or Secret, or to change the Sync back to Autotask and Set as Primary CRM options you chose in Step 3.

Refresh the page to confirm your changes saved.

Step 6 — Real-time sync

Companies and contacts from Autotask sync into Vendasta automatically whenever changes are made at the company or contact level on the Autotask side. This runs in the background — you do not need to stay on the page. Companies sync first, then contacts.

Step 7 — Verify the sync

  1. Open CRMCompanies in Partner Center.
  2. Look for a company that exists in Autotask.
  3. Confirm it appears with the correct name, phone, email, and address.
  4. Open a contact under that company — confirm it is linked correctly.

Done. Your Autotask integration is live. Changes sync in real time from this point forward.

Manage synced data

The integration syncs the following data types:

  • Companies — business name, phone, email, address, website (bidirectional)
  • Contacts — first name, last name, phone, email, address, company association (bidirectional)
  • Activity Feed notes — every sync event is logged on the record so you know what changed, when, and where it came from
  • Safe deletes — deleting a record in one system does NOT delete it in the other. An activity note is logged instead.

To manage what syncs, go to Settings on your Autotask connection page:

  • Sync back to Autotask selected — changes in Vendasta push to Autotask
  • Sync back to Autotask cleared — changes only flow from Autotask to Vendasta (one-way)

One-way vs. two-way sync

ModeRecommended whenWhat to expect
One-way syncAutotask is your primary source of truth and you want changes to flow into Vendasta only.Updates made in Autotask sync into Vendasta. Changes made only in Vendasta do not write back to Autotask.
Two-way syncYour team actively works in both systems and wants updates to stay aligned.Changes move in both directions. Agree ahead of time on who owns data quality and where edits normally happen, to avoid conflicting updates.

Integration example

Here is a real-world example of the integration in action:

  1. A partner adds a new contact, "Sneha Iyer", under the company "Le Royal Meridien" on the Autotask side.
  2. Within seconds, Sneha Iyer appears in Vendasta CRM under Le Royal Meridien — with a sync note in the Activity Feed confirming the event.
  3. The team updates Sneha Iyer's phone number in Vendasta. With Sync back to Autotask selected, the updated phone number flows back to Autotask automatically.
Sneha Iyer contact profile with Autotask sync activity notes

Roll the integration out gradually so you can confirm it behaves as expected before relying on it for every record:

  1. Start with one internal test company and one contact.
  2. Verify field mapping behavior and confirm the records appear as expected in both systems.
  3. Decide whether one-way or two-way sync best fits your team.
  4. Train administrators on where to update customer records going forward.
  5. Roll out to the broader team once the process is confirmed.

Troubleshooting

What you seeWhat is happeningHow to fix it
500 error when connectingAPI credentials are invalid or the user is disabledVerify credentials in Autotask Admin. Re-enter.
"Connected" but nothing syncsWebhooks are not enabled on the security levelOpen the security level in Autotask → Other Settings → enable webhooks with limit of 5+
Contacts not appearingContact is not linked to a company in AutotaskLink the contact to a company in Autotask. Unlinked contacts are skipped.
Duplicate records after connectingRecords existed in both systems without Autotask IDsDisconnect. Clean up duplicates. Bulk import with external_id. Reconnect. See Recovery section.
"Broken" status on connection cardAPI credentials expired or revokedClick Re-authenticate. Re-enter credentials.
Sync back to Autotask not workingThe record is missing its Autotask IDCheck the record in Vendasta. If autotask-company-id or autotask-contact-id is empty, use bulk import to add external IDs.

Recovery — already have duplicates?

If you connected Autotask before importing company and contact external IDs and now have duplicate records:

  1. Disconnect the Autotask integration from Integrations settings.
  2. Merge or delete duplicate records in Vendasta CRM.
  3. Prepare CSV files with Autotask IDs (follow the Bulk Import section above).
  4. Import companies first, then contacts — with external_id values.
  5. Reconnect the integration — sync will now match by external_id. No new duplicates.

Frequently asked questions

Can I still use Zapier with this integration?

You can, but we do not recommend it. Running both creates duplicate records. Disable your Autotask-related Zaps after connecting the native integration.

What happens if I disconnect?

Nothing is deleted. Records stay in both systems. Reconnecting later resumes sync from where it stopped.

Can I create a contact in Vendasta without associating it to a company?

Yes. Vendasta allows contacts to exist independently without a company association. However, standalone contacts will not sync to Autotask. Autotask enforces a mandatory company-contact relationship — every contact must belong to a company. If a contact exists in Vendasta without a company association, the integration will skip the sync and log an activity note indicating the contact was not synced.

How do I fix a contact that is not syncing to Autotask?

Associate the contact with a company in Vendasta. Once the company-contact relationship is established, the contact will be eligible for sync to Autotask on the next sync cycle.

Does this limitation apply to all integrations or only Autotask?

This is specific to Autotask. Each integration has its own data model requirements. Autotask strictly requires a company-contact hierarchy. Other integrations may handle standalone contacts differently depending on their own data model.

How fast does data sync?

Webhook-based — typically within seconds. If Autotask's API is slow, up to 1 minute.

Does deleting a record in Autotask delete it in Vendasta?

No. Deletes are non-destructive. An activity note is created. The record remains.

Can multiple users connect to the same Autotask account?

No. One connection per Vendasta account. The connection is account-level, not user-level.

What if I have contacts in Vendasta that are not in Autotask?

If they have matching email addresses, they will be matched during sync. If not, use the Bulk Import process to pre-populate Autotask IDs before connecting.

Is the data secure?

Yes. Direct API-to-API communication. Data encrypted in transit. No third-party intermediaries.

Why is my sync broken after a credential change?

Your API credentials may have expired. Check the integration card — if it shows "Broken" status, click Re-authenticate and re-enter your credentials.

Does the integration sync historical notes or all CRM activity?

No. The integration syncs company and contact records, and it logs sync events (creates, updates, safe deletes) to the Activity Feed as they happen. It does not retroactively import historical notes or mirror all past CRM activity from one system into the other.

How long does setup usually take?

Most partners can complete setup in 5 to 10 minutes if they already have Autotask administrator access and the required permissions in place. Add extra time for the bulk import step if you have existing records in both systems.