Halo PSA Data Migration Checklist

Halo PSA data migration seems complicated, but with a well-organized checklist, it becomes manageable. With the Help Desk Migration service, your transfer to Halo PSA goes without downtime or coding.

What Migration Wizard Will Import to Halo PSA:

What Data Won’t Be Transferred

Our automated data migration tool can’t import ticket tags, custom fields for organization and contacts, macros, triggers, automation, and other settings.

Before You Start Data Migration

For a successful data replication to Halo PSA, follow these steps.

Data Migration Process Planning

Every help desk migration is special; it depends on both your Source and Target platforms. There's no universal fix for every data movement. Based on what we've seen, there are two ways to go about it:

1. Automated data migration or DIY migration
2. Custom data migration
3. Automated or custom data migration + Delta migration

Need help planning and executing your service desk migration? Reach out to us, and we'll assist you in building your migration project.

Pre-migration Settings on Halo PSA Account

For a smooth Halo PSA data migration, go through these steps:

1. To connect Halo PSA, you need to provide

a. Authorisation Server: Click Configuration → Integrations → Halo PSA API → Authorisation Server.
b. Tenant: Press Configuration → Integrations → Halo PSA API → Tenant.
c. Client ID: Go to Configuration → Integrations → Halo PSA API → View Application → New.
d. Client Secret: Navigate to Configuration → Integrations → Halo PSA API → View Application → New.

2. Add all source agent profiles you want to import to Halo PSA and make sure they have accepted the team invitation. Open up Configuration → Teams & Agents → Agents → New → Details → Preferences → Save.

3. Create all source groups you need to shift to Halo PSA. Navigate to Configuration → Teams & Agents → Teams → New → type in Details, Agents, and Other → Save.

4. Set up all the source custom fields in Halo PSA. Navigate to Configuration → Custom Objects → Custom Fields → New → provide Details and Visibility Restrictions → Save.

5. Switch off Approval Process so ticket statuses migrate correctly. Go to Configuration → Tickets → Ticket Types → click on a ticket type → Edit. Select No in the Start an Approval Process field. Then press Save.

6. Turn off notifications during data migration. Open Configuration → Notifications → General Settings → clear the checkboxes for every notification.

Setting Up Halo PSA Data Migration

Try out our Demo Migration for a smooth data transfer. This way, you can test and adjust settings before the Full data transfer. Plus, you can re-run your trial Demo as many times as needed to get everything perfect.

Get started with your data migration to Halo PSA with these simple steps:

Step 1. Log into the Migration Wizard Account

Create a Migration Wizard account with Google, Microsoft, or your work email. If you opt for the work email, confirm it by following the instructions sent to your email.

Step 2. Connect Your Source and Target Platforms

The Migration Wizard provides helpful tips along the way, ensuring a smooth connection process. However, be ready that access credentials for connecting your source platform and Halo PSA may vary.

To connect Halo PSA as your Target platform, fill in Authorisation Server, Tenant, Client ID, and Client Secret.

Step 3. Choose What Records Will Be Moved

Choose the data entities you want to transfer to Halo PSA, then match them; that might be groups, agents, tickets, and articles.

Step 4. Match Groups

Select 'Match items' to map groups between the Source and Target platforms. If there are unassigned, inactive, or deleted groups, you can choose a default one. Or create any missing groups, whether it's one or multiselect, in Migration Wizard!

Click 'Save matching' to continue. If you need to re-run a Free Demo, use 'Auto match' for groups.

Step 5. Match Users

Choose 'Match items' for users to map agent profiles between the Source and Target platforms. If you have unassigned tickets, deleted or inactive agents, select a default agent for those records.

Click 'Save matching' to move to the next step. Use 'Auto match' for users if you re-run your trial Migration.

Step 6. Map Ticket Fields

When you select tickets, you'll see a window to map their fields. System fields like subject, group, and organization are mapped automatically. Check and set up default and custom ticket fields.

To map custom fields, set them up in Halo PSA first. When ready, click ‘Save mapping.’

Step 7. Map Article Values

Choose 'Map items' to match article fields. This is where you align article statuses between your Source and Halo PSA accounts. When done, click 'Save mapping' to continue.

Step 8. Out-of-the-box Automated Options

Your customization choices depend on your specific data movement—like from Zendesk to Halo PSA. Here's what you can customize:

• Move inline images as ticket attachments to keep customer data intact.
• Skip attachments. Though Migration Wizard typically moves all attachments, you can skip them for storage efficiency or faster data migration.
• Transfer call recordings as attachments for convenient future access.
• Demo with custom data to migrate 20 selected tickets and articles for a preview.
• Move side conversations into private notes to maintain customer context.
• Migrate content translations to maintain your Help Center multilingual.

Once you've finished mapping data, click 'Continue.' If there's anything you missed, the Migration Wizard will prompt you to review it.

What to Do After the Free Demo Migration

After completing your trial Migration to Halo PSA, follow these steps.

Verifying Demo Results

It's crucial to review the Demo migration results because the process mirrors the Full Data Migration. If some records didn't move in the trial, they won't transfer in the Full Data Migration.

Review reports for migrated, skipped, and failed records. Confirm each by checking IDs on the Source platform and Halo PSA.

What to Look for When Checking Migrated Data

• All comments moved, and the authors remain the same.
• Tickets assigned to agents correctly.
• Contacts and organizations migrated accurately.
• Articles moved with original statuses.
• Attachments transferred as expected.
• Demo data not affected by automation rules.

Managing Suspended Demos

If your Free Demo gets suspended, let our support team help you. Make sure they have access to your Halo PSA data integration for a speedy fix.

Choose Support Package

Help Desk Migration is here to assist with your data migration, no matter the requirements. Choose the plan that suits you, whether it's basic support or extras like Delta, re-migration, or Interval migration.

Discover the additional benefits included in Premium and/or Signature plans:

Price Breakdown and Payment

Check the detailed breakdown of prices to understand the Full Migration cost better.

When you're set, enter your billing information and click ‘Submit order’ to complete the payment.

Give Access to Your Colleagues and Customize the Migration Name

If the mapping step feels a bit tricky, consider teaming up with a colleague. Just share access to your Halo PSA data transfer in a few clicks.

You can control the access level—determine if it's full or restricted access, and if required, you can withdraw it.

Stay organized—label each data migration for swift and straightforward identification.

Start Full Data Migration

After your payment is confirmed, go back to the Migration Wizard. Remember, keep things smooth by avoiding last-minute changes.

If you're ready, start your Full Data Migration right away. Or, pick a time that works for you and click "Save schedule."

The time it takes to move your data depends on the number of records. Typically, it's about 2000 tickets per hour on average. If you want it faster, ask your vendors to boost your API limits. Just let us know before you kick off your Full Data Migration.

Got questions? Our support team has your back for a smooth Halo PSA data replication.