TracePharma

Guide

Migrate from TraceLink without a rip-and-replace

If US DSCSA is the job and partners are known, dual-run TracePharma beside Opus until outbound ACKs are clean. Do not cut over mid-inspection. We will tell you if you should stay.

Partners do not go dark because EPCIS is a standard. They go dark when credentials, GLN routing, and ACK expectations are not re-pointed. The hard part is reconnection, not the event format.

When to stay on Opus

Stay if you onboard thousands of unknown partners, you need global regulation modules, or renewal is cheaper than migration. Read the stay vs move table. TracePharma is not an Opus replacement.

Cutover sequence

  1. List the partners you actually exchange with. Names, GLNs, transport (AS2, SFTP, HTTPS).
  2. Stand up a TracePharma tenant on your profile. Provision inbound presets. Run a test receive.
  3. Dual-run: partners send to both systems, or you accept on TracePharma while Opus still ships, until ACKs are clean.
  4. Keep inspection evidence in the system of record that still holds it. Do not freeze a cutover during an active inspection.
  5. Re-point remaining partners. Watch ACK health per customer. Then retire the Opus workflows you no longer operate.

What we walk on the demo

Partner list, transport paths, dual-run order, and whether Opus is still the right network for part of the list. We reply within one business day.

Map a parallel pilot. We will tell you if you should stay.

Bring two supplier names and how they send files today.

30–45 minutes on a profile-tuned workspace. We reply within one business day.

Map a parallel pilot