# Validating your migration to Amazon MQ
<a name="tibco-testing-and-validation"></a>

 In the [Which TIBCO EMS architectures are used for migrating to Amazon MQ?](tibco-ems-typical-architecture.md) section, a *Topic to Queue* bridge was used to forward messages to other EMS servers. In Amazon MQ, *App 1* would send messages directly to `Q1` because messages on a queue are forwarded in a [Network of Brokers](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/network-of-brokers). 

 In the TIBCO EMS example, messages from *App 2* are sent to `Q2` and then forwarded to `Q2@EMS_APPLE`. In Amazon MQ, the queue name, `Q2`, would be the same on both message brokers, simplifying the configuration of *App 1*. 

 The following example shows the **AMQ\$1ORANGE** broker with consumers in *us-east-1* and **AMQ\$1APPLE** with consumers in *us-east-2* ![\[ActiveMQ interface showing two queues, Q1 and Q2, each with one consumer and no pending messages.\]](http://docs.aws.amazon.com/amazon-mq/latest/migration-guide/images/tibco-testing-and-validation-fig-1.PNG) ![\[ActiveMQ web interface showing two queues with 1 consumer each and no pending messages.\]](http://docs.aws.amazon.com/amazon-mq/latest/migration-guide/images/tibco-testing-and-validation-fig-2.PNG)