Hi Karthik,

Yes you can use ITSM Bridge to do this;

When migrating from Instance B, define the primary key for each form mapping in 
the form mapping definition.  Then you can control the behaviour as follows:

If the target record exists on your new instance and you don’t want to 
over-write, set the option to skip.
If the target record exists and you want to update it with values from instance 
B, set the option to Update.
If the target record exists but you want to create another copy - use the 
assignment mapping to prefix or suffix the primary key field to make the target 
record unique.

Hope that helps

Mark Herring

itsmbridge.com



















> On 3 Jul 2018, at 11:00, [email protected] wrote:
> 
> Send ARSList mailing list submissions to
>       [email protected]
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>       https://mailman.rrr.se/cgi/listinfo/arslist
> or, via email, send a message with subject or body 'help' to
>       [email protected]
> 
> You can reach the person managing the list at
>       [email protected]
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ARSList digest..."
> 
> 
> Today's Topics:
> 
>   1. RE: Renaming Business Service Names (Ben Chernys)
>   2. Data Migration after upgrade from 2 disparate ITSM instances
>      (karthik manoharan)
>   3. Data Migration after upgrade from 2 disparate ITSM instances
>      (Manoharan, Karthik)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 2 Jul 2018 09:12:31 -0600
> From: "Ben Chernys" <[email protected]>
> To: "'ARSList'" <[email protected]>
> Subject: RE: Renaming Business Service Names
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
> 
> Meta-Databot works like the BMC Data Wizard but is automated and extensible.
> It processes spreadsheets of changes.  
> 
> 
> 
> Putting up a new Data admin config is as easy as adding a new sheet to the
> configuration Excel file.
> 
> 
> 
> Meta-Databot is free with Meta-Update and we would put up the new
> configuration sheet for you.
> 
> 
> 
> 
> 
> 
> Cheers,
> 
> Ben Chernys
> Senior Software Architect
> 
> 
> Canada / Deutschland
> Mobile:    +49 171 380 2329   GMT - 7 + [ DST ]
> 
> Mobile     +1 403  554 0887
> Email:        <mailto:[email protected]>
> [email protected]
> Web:          <http://www.softwaretoolhouse.com/> www.softwaretoolhouse.com
> 
> We are a BMC Technology Alliance Partner
> 
> 
> 
> 
> 
> Check out Software Tool House's free Diary Editor and our  Freebies Section
> for ITSM Forms and Fields spreadsheet.
> 
> <http://www.softwaretoolhouse.com/product/SthMupd/index.html> Meta-Update,
> our premium ARS Data tool, lets you automate your imports, migrations, in no
> time at all, without programming, without staging forms, without merge
> workflow. 
> 
> 
> 
> <http://www.softwaretoolhouse.com/product/SthArch/index.html> Meta-Archive
> does ITSM Archiving your way: with your forms and your multi-tenant rules,
> treating each root request as a complete tree and checking associatuions.
> Archive output to different servers, HTML pages with links to attachments or
> archive forms.
> 
> 
> 
> <http://www.softwaretoolhouse.com/product/Databot/index.html> Meta-Databot
> is an automated, extensible BMC Data Wizard.  It reads a file of data
> changes and sports an Undo feature.
> 
> 
> 
> Pre ITSM 9.1.04?  Clarify?  HP? Roll your own?  No problem!  You can keep
> your valuable data!
> 
> 
> <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> From: ARSList <[email protected]> On Behalf Of
> [email protected]
> Sent: June-29-18 9:47 AM
> To: [email protected]
> Subject: Renaming Business Service Names
> 
> 
> 
> Hi Guys,
> 
> Is there any easy way of renaming the business service CI in ITSM and its
> related transactional references in the system ie. Incident, change etc ?
> 
> 
> 
> Regards,
> 
> Guru
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <https://mailman.rrr.se/arslist/attachments/20180702/424e251c/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image003.jpg
> Type: image/jpeg
> Size: 2441 bytes
> Desc: not available
> URL: 
> <https://mailman.rrr.se/arslist/attachments/20180702/424e251c/attachment.jpg>
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 3 Jul 2018 09:51:08 +0530
> From: karthik manoharan <[email protected]>
> To: [email protected]
> Subject: Data Migration after upgrade from 2 disparate ITSM instances
> Message-ID:
>       <cabiyatl-qcxejggvhfmgwde-8hukjme0zqtwcq0_oq5zji7...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hello Listers,
> 
> Currently there are 2 different ITSM environments A and B running on
> different version 7.6 and 8.1.
> 
> I?m planning to setup a single ITSM instance 9.1 by installing a standalone
> ITSM instance and migrating foundation data from 2 disparate ITSM instances
> (A+B).
> 
> 
> 
> I?ve explored BMC Delta Data Migrator and found that we could use the same
> to migrate from instance A.
> 
> Let's assume I've migrated from instance A. The problem arises when
> performing migration from the second instance B. There are would be lot of
> duplicate records(which might not be actually duplicate but from instance A)
> 
> DDM would identify matching unique index values and may have different
> Request ID/ Instance ID values from instance A.
> 
> This would involve lot of manual activity to validate and delete in case of
> duplicates, but most of the cases we would like to retain records from both
> servers.
> 
> Is there any suggestions for any other tool for data migration or any
> different approaches for the same.
> 
> Regards,
> 
> Karthik.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <https://mailman.rrr.se/arslist/attachments/20180703/2c4c0da8/attachment.html>
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 3 Jul 2018 04:26:12 +0000
> From: "Manoharan, Karthik" <[email protected]>
> To: "[email protected]" <[email protected]>
> Subject: Data Migration after upgrade from 2 disparate ITSM instances
> Message-ID:
>       <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hello Listers,
> 
> Currently there are 2 different ITSM environments A and B running on 
> different version 7.6 and 8.1.
> I'm planning to setup a single ITSM instance 9.1 by installing a standalone 
> ITSM instance and migrating foundation data from 2 disparate ITSM instances 
> (A+B).
> I've explored BMC Delta Data Migrator and found that we could use it to 
> migrate from instance A.
> Let's assume I've migrated from instance A. The problem arises when 
> performing migration from the second instance B.
> 
> There are would be lot of duplicate records(which might not be actually 
> duplicate but from instance A)
> DDM would identify matching unique index values and may have different 
> Request ID/ Instance ID values from instance A.
> This would involve lot of manual activity to validate and delete in case of 
> duplicates, but most of the cases we would like to retain records from both 
> servers.
> 
> Could you please help with any suggestions for any other tool for data 
> migration or any different approach for the same.
> 
> Thanks in advance.
> 
> Regards,
> Karthik.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <https://mailman.rrr.se/arslist/attachments/20180703/c47e7d00/attachment.html>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> ARSList mailing list
> [email protected]
> https://mailman.rrr.se/cgi/listinfo/arslist
> 
> 
> ------------------------------
> 
> End of ARSList Digest, Vol 30, Issue 1
> **************************************

-- 
ARSList mailing list
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist

Reply via email to