Page Comparison

1

• Create replica journeys in WMC

• Bulk update domains

• Have a lot of efforts/don’t want to update every effort

• Have a lot of offers/don’t want to update the offers in IRIS

• Less updates in IRIS

• Don’t need to update the domain of every single effort

• No downtime with the transition from OPIUM to WMC

• Discovery/QA required upfront

• Need to review all the efforts tied to the domain/item and coordinate creation of WMC journeys before making any domain changes

• Potential for mismatched domains as part of bulk change

  • Would need to be sure that all the journeys tied to the efforts with this assigned domain have been set up in WMC with the SAME URL nickname that was used in OPIUM. If something doesn’t exist, there will be an error

2

• Create journeys in WMC

• Retire OPIUM offers in IRIS

• Redirect to WMC journey

• Bulk update domains

• Have a lot of efforts/don’t want to update every effort

• Don’t want to use the same offer and set up a journey that has an identical url nickname in WMC as OPIUM

• Less updates in IRIS

• Don’t need to update the domain of every single effort

• May be some down time for the order forms between retiring the offers and switching the domains – should be minimal

• Discovery/QA required upfront

• Need to review all the efforts tied to the domain/item and coordinate creation of WMC journeys before making any domain changes

3

• Update domains on the individual effort level

• Don’t want to do a lot of discovery/QA upfront to organize what you’re going to migrate

• Note: Most manual option

• Don’t need to worry about mismatched domains as part of a bulk change – won’t be editing the domain configurations in IRIS

• Less discovery/QA upfront

• More IRIS work - need to update each individual effort

• Note: same amount of work in WMC as options 1 and 2