SMARTshift Integration Survey: This quick survey gathers the key details needed to customize your SMARTshift experience LET'S MAKE SHIFT HAPPEN! Want to go back and learn more about SMARTshift? Click here. ACQUIRED MSP STUFF Let's get some quick answers on a few important things. What is the name of the acquired MSP?(Required)What was the acquisition date? MM slash DD slash YYYY What is the planned go-live date? MM slash DD slash YYYY What time zone are they in?(Required) Eastern Central Mountain Pacific Is the inbound PSA data from an on-premise instance or cloud instance?(Required) Cloud On-Premise Inbound PSA Platform(s) In Use(Required) Asana AutoTask ConnectWise Fresh Desk Halo Harvest HubSpot ProCore SalesForce ServiceNow Zoho Custom - SQL Other 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! You know you have to contact ConnectWise about a sandbox(Required) Yes No Sandboxes are for kids so why do I need one DATA PRE-PEND (3-digits) Pre-pending allows us to place 3-digits 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: https://www.decisiondigital.com/docs/SS_prepend.pdf Pre-pend (3-digits) for tagging the arriving data(Required)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. Check out the full list here: www.decisiondigital.com/docs/SS_dependencydata.pdf Wow! That's a lot of data. I've checked out the list(Required) Yes No Not sure what I am looking at but it's impressive 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 I understand that I need to build out these three areas in the destination database(Required) Yes No I am confused and have no idea Did you review the dependency dataset list?(Required) Yes No Maybe STANDARD INTEGRATION DATASETS STANDARD INTEGRATION DATASETS Scoped as a predictable amount, up to the record limit indicated. Larger datasets would be handled out-of-scope. Companies Dataset 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 COMPANIES(Required) Active Only Active + Inactive Contacts Dataset Contacts Contacts are embedded in many areas, including tickets, activities, and more. There are 1 filter / 62 selectable fields. CONTACTS(Required) Active Only Active + Inactive Product Catalog Dataset 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 PRODUCT CATALOG(Required) Active Only Active + Inactive None Activities Dataset 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 ACTIVITIES(Required) Open Open + Completed None Boards - Service Dataset Boards - Service There are loads of adjunct datasets and dependencies around boards. 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 BOARDS - SERVICE(Required) Active Only Active + Inactive None Service Tickets Dataset Service 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 tickets can be placed in SMARTchive for easy access. There are 4 filters / 116 selectable fields: Cut-Off Date Attached service board Status SERVICE TICKETS(Required) Active None Boards - Project Dataset Boards - Project There are loads of adjunct datasets and dependencies around boards. 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 BOARDS - PROJECT(Required) Active Only Active + Inactive None Projects + Project Phases + Project Sub-Phases Dataset Projects + Project Phases + Project Sub-Phases We recommend only moving active projects. Please be aware that project numbers and project ticket numbers WILL CHANGE. Historical data can be placed in SMARTchive for easy access. There are 4 filters / 80 selectable fields: Project closed Project status Attached project board PROJECTS + PROJECT PHASES + PROJECT SUB-PHASES(Required) Open Open + Closed None Projects Tickets Dataset 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 PROJECT TICKETS(Required) Active None Agreements Dataset Agreements Agreements are dependent on additions and the product catalog. Also, for proper billing, the agreement billing start date (not the agreement start date) must be reset to a future date, after the migration has been completed. There are 3 filters / 82 selectable fields, including: Cancelled Type Status AGREEMENTS(Required) Active Active + Cancelled None Agreement Additions Dataset Agreement Additions For proper billing, the addition effective data must be updated after the migration has been completed. Due to dependencies, there are no filters but 32 selectable fields. AGREEMENTS ADDITIONS(Required) All None Configurations Dataset Configurations Due to dependencies, there are no filters but 58 selectable fields. CONFIGURATIONS(Required) All None REWIRE DATASETS 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. PSA - SERVICE TICKET TEMPLATES(Required) Yes No PSA - PROJECT TEMPLATES(Required) Yes No PSA - STANDARD NOTES(Required) Yes No PSA - EMAIL TEMPLATES(Required) Invoice Email-Services None PSA - EMAIL CONNECTOR(Required) Email Connector Email Connector Rule None PSA - WORKFLOWS(Required) Yes No CPQ - QUOTE TEMPLATES(Required) Yes No SMARTCHIVE DATASETS SMARTCHIVE DATASETS Select all of the data sets to include in SMARTchive AI-fueled data lake service. Historical Data Service Tickets Project Tickets Opportunities Quotes Agreements Purchase Orders Sales Orders I don't need SMARTchive Name(Required) First Last Email(Required) CommentsThis field is for validation purposes and should be left unchanged. Δ
