Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Contact → Move to Company
AI-generatedOverview
This node operation moves a contact from one company to another within the Autotask PSA system. It is useful for scenarios where contacts need to be reorganized or reassigned to different companies, such as during company mergers, restructuring, or data cleanup. The operation supports options like dry run for previewing changes, handling duplicates by skipping moves if a duplicate email is found, and copying related data such as contact groups, company notes, and note attachments.
Use Case Examples
- Moving a contact with ID '123' from Company A to Company B with ID '456', copying all related notes and groups.
- Performing a dry run to preview the migration plan without making any changes.
- Skipping the move if a contact with the same email already exists in the destination company to avoid duplicates.
Properties
| Name | Meaning |
|---|---|
| Source Contact ID | The ID of the contact to move. |
| Destination Company ID | The ID of the company to move the contact to. |
| Dry Run | Whether to return a migration plan without executing any writes, useful for previewing what would happen. |
| Destination Location ID | Location ID at the destination company. Leave blank to auto-map by location name, or enter a specific ID. |
| Skip If Duplicate Email Found | Whether to skip the move without error when a destination contact already exists with the same email address. |
| Copy Contact Groups | Whether to copy the contact's group memberships to the new contact. |
| Copy Company Notes | Whether to copy CompanyNotes linked to this contact (via contactID). |
| Copy Note Attachments | Whether to also copy attachments on those CompanyNotes (max 6MB per file). |
| Source Audit Note | Note left on the source company with placeholders for contact and company details. |
| Destination Audit Note | Note left on the destination company with placeholders for contact and company details. |
| Impersonation Resource ID | Optional resource ID to impersonate. Created records will be attributed to this resource. Leave blank to use the credential user. |
| Proceed Without Impersonation If Denied | Whether to proceed without impersonation when denied. Applies only when Impersonation Resource ID is set. |
Output
JSON
migrationPlan- Details of the migration plan when dry run is enabled.movedContactId- The ID of the newly created contact in the destination company after the move.skippedDueToDuplicateEmail- Indicates if the move was skipped because a duplicate email was found in the destination company.auditNotes- Audit notes left on source and destination companies documenting the move.
Dependencies
- Autotask PSA API with appropriate credentials for authentication and authorization.
Troubleshooting
- Errors may occur if the source contact ID or destination company ID is invalid or missing.
- If duplicate emails exist and skipping is disabled, the operation may fail or create duplicates.
- Impersonation may fail if the resource ID is invalid or lacks permissions; enabling proceedWithoutImpersonationIfDenied can help.
- Attachments larger than 6MB cannot be copied and may cause partial failures.
Links
- Autotask PSA REST API Documentation - Official API documentation for Autotask PSA, useful for understanding API capabilities and limitations.