SMARTshift ConnectWise Data Merge Survey

ACQUIRED MSP STUFF

Let's get some quick answers on a few important things.

SANDBOX DATABASE

Messing up live data? Yeah, let's not. When merging data, we play it safe—everything goes into a sandbox first. To set one up, you'll need to give ConnectWise a shout and arrange a synced database. Better safe than sorry!

DATA PRE-PEND (3-characters)

Pre-pending allows us to place 3-characters in front of certain datasets (think product catalogs, board names, statuses, etc.) to prevent data over-writes and to help you easily identify the origin of the data. This makes it easier to manage, trace, and optionally remove the data later if it's no longer needed.

You can review the full list of applicable datasets HERE

DEPENDENCY DATASETS

Welcome to the dataset bonanza! To rock the standard integration datasets, you have to have the connected datasets too! It's a wild ride with over 100 dependency datasets, but don't worry, we're the experts at moving them over seamlessly.

We DISABLE the default checkbox for all dependencies prior to merging, to prevent the unexpected over-writing of default settings in the destination database.

You can review the full list of applicable datasets HERE

REMAP DATASETS

Get ready for some database magic! When companies merge, names sometimes change like a chameleon. Imagine James.Kirk becoming JKirk. We'll help you navigate this transformation with ease. There are three key areas to remap. First, we need you to build them in the destination database. Next, we'll work together to map them before integration:

• Member IDs
• Departments
• Locations
• Priorities

MAPPED MEMBER IDS NEED TO BE ACTIVE IN THE SANDBOX AND PRODUCTION.

STANDARD DATASETS

Scoped as a predictable amount, up to the record limit indicated. Larger datasets would be handled out-of-scope.

Companies

Companies are a "connector" dataset for many other areas and are required. There are 3 filters / 70 selectable fields:

• Company/Vendor Name
• Type
• Status

Contacts

Contacts are embedded in many areas, including tickets, activities, and more. There are 1 filter / 62 selectable fields.

Product Catalog

We recommend only moving active products and their associated datasets. Required for Agreements & Additions. There are 2 filters / 47 selectable fields:

• Item Names
• Categories

Activities

We've added a cut-off date filter so you can choose to migrate all activities after a certain date. There are 3 filters / 25 selectable fields:

• Cut-off date
• Type
• Status

Boards - Service

There are loads of adjunct datasets and dependencies around boards. This includes service boards and Streamline IT boards (if you use them)They are required for ticket migration. You can always consolidate them within the new database. There are 4 filters / 64 selectable fields:

• Board Name
• Location
• Department

Projects Tickets

Please be aware that ticket migrations are tricky due to other data that may have changed (or no longer exists) during migration. Ticket numbers WILL CHANGE. We recommend ONLY active tickets. Historical data can be placed in SMARTchive for easy access. There are 4 filters / 80 selectable fields:

• Cut-Off Date
• Attached service board
• Status

FOR ACTIVE TICKETS THAT COME OVER, ALL MEMBER ID'S ASSOCIATED WITH IT ARE ACTIVE IN SANDBOX AND PRODUCTION.

Configurations

Due to dependencies, there are no filters but 58 selectable fields.

REWIRE DATASETS

During migration, certain data may require rewiring due to changes that occur. It's like moving into a new house and realizing the furniture doesn't fit! This section addresses the necessary adjustments for datasets that might lose their old settings or names in the new database. We'll review them with you to ensure everything works seamlessly post-migration, so your data feels right at home. We will scope them on a T&M basis.

SMARTCHIVE DATASETS

Select all of the data sets to include in SMARTchive AI-fueled data lake service.