Replacing a system, bringing businesses together or integrating an acquisition into a group: connect old and new environments with Service Automation Suite. We guide workflow configuration and the phased transition, retaining relationships, rules and checks that still fit.
Working from Canon? We connect the transition to your existing workflow.
Keep your processes in charge. Change your tools.
Your processes
Onboarding & departure
Service requests
Asset management
Workflow logic & control
Service Automation SuiteYour matrices, relationships, decision rules and workflow steps
Integration layer
Current connection
New connection
Product layer
Current HR applicationFor example, AFAS
New HR applicationFor example, Youforce
This is the benefit: when workflow logic is configured in Service Automation Suite, changing products does not mean rebuilding it from scratch. We adapt the connection and product-specific mapping, reuse what still fits and verify execution with the new application.
What do you want to change?
Service desk
A different service desk. Bring ongoing work with you.
Your municipality, healthcare organisation or IT provider chooses a different service tool, such as moving from Jira Service Management to HaloITSM or the reverse. Customer requests, owners and progress need to remain traceable in the new environment.
The new service team can identify and continue outstanding work, with a reference to the original request.
See how we configure this
Select organisations, contacts, open requests and required history. Retain original references and agree where attachments and older records remain accessible.
Relate source and destination records through Service Automation Suite. Map statuses, priorities and support groups to your working agreements. Keep transition-period replies attached to the right record.
Check whether a request can continue in the new environment with the right customer, owner, status and feedback. Approve a selected team or customer group before moving the next one.
HR
A new HR system. Keep the employee journey connected.
You replace the HR source, for example around AFAS or Youforce. IT and facilities still need current employee, role, location and effective-date information. The transition needs to support onboarding, changes and departures.
Replace the source and remap its data while retaining suitable employee relationships, rules and follow-up workflows in Service Automation Suite.
See how we configure this
Relate employee and employment identifiers from both sources to the same person. Surface discrepancies, missing values and multiple employments.
Connect the new source to the agreed access, equipment and task matrix. Define when the new HR system becomes authoritative for each field.
Test the employee journey with a limited selection. Check existing accounts and equipment before starting new actions and have HR and IT review the outcome.
Assets
From separate asset lists to a usable register.
Supplier lists, spreadsheets and inventory from Jamf, Intune or Lansweeper describe overlapping equipment. You want a new CMDB or asset model with clear ownership and a usable lifecycle.
A verified starting register and a configured check that can continue after migration.
See how we configure this
Compare serial numbers, external asset IDs, sites and people. Review duplicate or uncertain matches and define the authoritative source for each field.
Build agreed assets and relationships in the new register. Retain source references and connect supplier, employee, site and status where interfaces support them.
Compare the new register with available operational observations. Give missing enrolment, incorrect assignments and unexplained discrepancies an owner and follow-up action.
Cloud
From on-premises to cloud. Move the data flows too.
An application or database moves to another environment. Surrounding requests, data exchange and follow-up actions need to work through the new connection, for example when an on-premises SQL source starts supplying a cloud service.
Connect the application move to changes and checks for the workflows that depend on it.
See how we configure this
Map existing data flows, authentication and dependencies. Agree with IT how to reach the local source and new environment, for example through an appropriate Service Automation Suite Agent setup.
Adapt source or destination calls and field mappings. Reuse suitable workflow conditions and checks. Test whether dates, codes and errors retain the same meaning.
Compare processing through the new route with the agreed outcome. Plan cutover, process remaining changes and verify the first real workflow outcomes afterwards.
Supplier
A different supplier. Transfer work and working agreements.
Your organisation changes IT provider, or an MSP takes over a customer. Open tickets, assets, contacts and service agreements need to reach the right party, with a clear boundary around each customer.
A handover aligned with service delivery, with visibility into outstanding work, discrepancies and the new owner.
See how we configure this
Agree which customer data and outstanding work transfer, which history remains accessible and who may approve the selection. Retain internal and external references together.
Configure transfer and map statuses and responsibilities. Define how transition-period replies reach the same ticket and prevent duplicate execution when data is resubmitted.
Compare supplied, received and outstanding work per customer. Have both parties confirm the agreed handover and assign owners to exceptions.
Organisation
Mergers and acquisitions. Bring organisations together.
Organisations grow, merge or acquire businesses. Teams, applications and customer environments come together or are reorganised. The same person, customer, site or asset may appear in several sources. Establish which record is authoritative and how data, responsibilities and working agreements fit the new organisation.
A phased transition reconnecting data, ownership and service delivery.
See how we configure this
Define new organisational boundaries, source owners and identifiers. Establish which records belong to each unit and what information may be shared.
Relate old and new organisation, person and asset IDs in Service Automation Suite. Map team, site and ownership and connect the outcome to the new workflow rules.
Review data selections, relationships and access actions. Transition by site, team or customer and verify that work and feedback reach the correct organisation.
Build on what works
Your application changes. Build on your existing foundation.
Already running your workflow in Service Automation Suite? Retain what fits and adapt the connection where needed. Avoid rediscovering relationships, working agreements and checks each time.
Define sources, destinations, selections and owners. Agree what to migrate, clean up or retain in an accessible archive, including attachments and confidential information.
Configure the mapping
Define identifiers, field mappings, relationships, statuses and conditions. Choose the authoritative source for each field and how errors or uncertain matches receive review.
Trial a limited selection
Read a defined set, verify its mapping and write to the destination under the agreed approval. Check relationships and follow-up workflows as well as record counts.
Manage the transition
Work by team, site or customer group. During parallel operation, define who may write, how new changes are processed and how repeated processing is recognised.
Cut over and keep checking
Have the process owner approve agreed checks. Plan final changes and fallback: what can be restored and which actions require separate recovery? After cutover, track errors, backlogs and confirmed outcomes.
Available interfaces, permissions and destination setup determine which data, history, attachments and actions can transfer. We assess this before execution and establish what can be configured and where additional development or manual work is needed.
Within the same application too. For example, TOPdesk.
Moving from Configuration Management to Asset Management is a migration too. Service Automation Suite connects agreed records, relationships and follow-up workflows to the new setup in the sequence that fits your organisation.
