At 4:40 on a Friday in Columbus, Ohio, a benefits coordinator named Maya has her cursor over “Resend invitation.” The employee's old gift page says an address is missing, but the warehouse report has a tracking number against the same anniversary award. The new company portal opens Monday. Maya closes the resend window and asks the warehouse whether that number belongs to a parcel that left the building.
Maya and her company are fictional. The choice is familiar to anyone closing a program during a merger. A new inbox can answer the employee on Monday, but somebody still needs to finish the original gift. The safest route depends on what happened to that claim. This guide shows how to find that out, when to leave the work with the old provider, and how to move the rest without opening a second path to the same gift.
Start with the record the employee is asking about
Maya's ticket should open against the anniversary award. Her team can use the original program and claim number to join the invitation, employee selection, and warehouse records. An employee might hold two valid awards, so the person's name or work email cannot do that job alone. A delivery address is even less reliable. The household may have several recipients, and the address can change between accepting an award and choosing a gift. If the old provider has no stable claim number, give the award an internal reference and keep a restricted record of the provider references that belong to it.
Put a few concrete facts on each line. Include the offer and deadline the employee was given, whether the employee selected an item, the last action the fulfillment provider confirmed, and the next person who can act. The report should say when each source was checked. A Thursday morning invitation export and a Friday afternoon warehouse report will show different stages for some people. Ask the provider for changes through the handoff time, especially acceptances or shipment activity that could turn an apparently open invitation into an existing order.
Maya has three questions for the warehouse. Does this tracking number correspond to the same award and item? Was it only printed, or did the carrier receive the parcel? If the carrier received it, who can check its status after the merger? A shipping label can exist before dispatch. A delayed warehouse report can also make a real dispatch look absent. Until somebody can tell which event occurred, her record belongs in an exception queue with a named investigator and a follow-up time.
The other rows need the same care at scale. Give HR ownership of the original terms and recipient eligibility. Have the provider confirm the selection and the warehouse confirm its own release, dispatch, and return events. Ask procurement who can obtain those records after the old contract changes, and ask finance which cost center can pay outstanding invoices. Those decisions tell Maya whether the help desk can promise an answer or only take a message.
Case one: Keep the old claim page open past the new portal launch
In Maya's example, a regional employer has 200 approved anniversary awards on its closing inventory. The teams verify that 123 are fulfilled. Forty-two invitations are still open and eligible. Another 29 employees made selections that the fulfillment team is still processing. The six remaining records contain conflicting or missing evidence, including Maya's ticket. Every row needs a route, even when its next action is simply to wait for a specific piece of evidence.
On the cutover call, procurement learns the old provider can keep the anniversary page and returns service available for six weeks. That window covers the remaining advertised claim dates, and finance can pay under the transition agreement. The new employee portal can list a support contact, but the new gift platform would require importing the 29 selections and separately testing shipment status. Maya's team keeps the 42 open invitations and the 29 pending selections with the original provider. The five other unresolved cases and Maya's ticket stay with the new help desk for individual investigation. The 123 fulfilled awards remain visible for lookup and do not receive new invitations.
| Route | Choose it when | Ask for this evidence |
|---|---|---|
| Finish with the old provider | The original terms still apply, links are usable, and the provider can support delivery and returns through the agreed dates. | An approved test claim, status and return access, a support owner, and an agreed end date. |
| Move verified open claims | The successor can carry the original offer, deadline, and stable claim reference, and the old route can stop accepting those same claims. | A mapping by claim, a record of the last change on the old route, and a tested import that recognizes a repeat. |
| Handle individual exceptions | The old route is unsafe or unavailable, the employee's identity needs checking, or the order outcome remains unclear. | A restricted support record, original eligibility and fulfillment evidence, and an owner who can approve the next action. |
A six-week extension needs more detail than “links stay up.” Define the last date the provider will accept a selection and the last date it can investigate a late delivery. A person who selects a gift on the final eligible day may still need help after the page closes. Ask who handles a return already in transit when the support agreement ends. Give finance an invoice contact and a separate cutoff for credits. If the provider cannot cover those obligations, narrow the population that stays on the old route and decide who will finish the rest.
The program notice and the service agreement may use different clocks. The original email might say employees have until midnight Friday to choose, while the vendor's last support shift ends at 5 p.m. Pacific. Record the time zone attached to each deadline and confirm what happens to a valid selection submitted between those events. When the agreement does not cover the promised claim window, bring the gap to HR and procurement before you notify employees. They can ask for an extension or approve a way to complete affected claims, then tell employees exactly what to do.
Before Monday, Maya's team tries the old page from an approved test account and contacts support through the new portal. The help desk can look up the test record by claim reference and request a provider response without asking the employee to forward a live claim link. HR checks that someone who has lost access to the old mailbox still has an authorized path to help. Maya can now tell the person with the tracking number when she will follow up. Her team has kept the first award traceable through a branding change while the provider works on the answer.
Case two: Move 43 invitations when the old domain goes dark
Imagine a separate employer that is retiring a co-branded site at 6 p.m. Central on Friday. It has 71 grants to account for. The provider's first report has 43 unclaimed invitations, 21 accepted selections, and seven records with conflicting states. The warehouse proves that five of the 21 have shipped. The successor system can preserve the old claim reference and deadline for an unclaimed award, but it cannot import a previously selected product.
The operations lead plans to move the 43 unclaimed records if a final check confirms that all 43 are still open. The 16 accepted but unshipped selections continue with the original fulfillment team under a short service arrangement. The five shipped items go to a support lookup. Seven need an individual investigation. If procurement cannot arrange a service tail for the 16 orders, the lead must settle that with the program owner before the domain goes dark. A working successor page for the unclaimed group does not give the other 16 employees a way to receive the products they selected.
A day before the change, the lead and the old provider agree on when to stop accepting the 43 claims. They keep the claim history available for reconciliation. The provider checks for requests submitted before the stop whose confirmations arrived afterward. A late acceptance would remove a record from the import and put it into a fulfillment decision. The lead compares claim references and checks the count again. In this case, the final report confirms all 43 remain open.
The successor import reports that it accepted 42 rows and rejected one because the employee's contact could not be matched. The operator retains the response by row, confirms that the old claim is disabled, and corrects the contact through the approved employee directory. The corrected record still carries the original claim reference and its deadline. The operator processes that record on its own. If the import had timed out without saying which rows it accepted, the next step would have been a lookup or provider review of those references before any further import.
The final check accounts for all 71 grants as 43 in the successor system, 16 still being fulfilled, five available for shipment lookup, and seven in an exception queue. The sum helps catch a missing group. Matching the individual references catches a duplicate and an omission that happen to cancel out in the total. For the person whose contact failed, the lead can show the original approval, the disabled old route, the corrected contact, and exactly one live claim in the new system.
Do a second check after the first invitations go out. An export that said “unclaimed” before the cutover might appear again after it, even though the old system has since been closed. A worker should be able to identify the export's cutoff and distinguish it from the current record. Keep the approved migration list and the response by claim in a controlled location. If someone proposes to use a backup export to recover a missing invitation, first check whether that claim was accepted, rejected, or deliberately left out. This step gives the operator a basis for deciding whether an individual repair is possible.
Put the new path through the employee's test
An import receipt tells you the successor system received records. Ask an employee tester to start where a real recipient will start. Can the tester find the new page from the employee portal? Does identity verification admit the right person? Does the offer still show the original terms and deadline? After selection, can support find the confirmation using the original reference? If the employee instead opens the old invitation, does it show a safe help route without accepting the same claim a second time?
Use invented records to exercise several states. Include an invitation that was never used, a selected gift waiting for an address, an order that already shipped, a record with a changed email address, and an offer that expired before the test date. Re-run the same authorized import or request under the provider's documented test conditions. Check that it leaves one open claim for an eligible employee and generates no new dispatch for the already shipped one. Save the counts, reference-level results, and the specific configuration tested so the launch team can repeat the critical checks after the live domain change.
Set a condition for stopping before the first recipient sees the new page. If both routes accept the same claim, if a group sees the wrong deadline, or if support cannot look up the affected orders, stop that group's new requests. Keep the evidence for any claims already accepted. The warehouse may have acted while the team was examining the portal, so get actual release and shipment results before reopening the old route. If a package has already left, the people handling that order will need a fulfillment decision. Reverting the link does not recall a parcel.
Write down who can pause a group, who can confirm a shipment, and who can approve a replacement. Assign a response time to the individual exceptions that will outlast the cutover. If an employee reports a broken link, the help desk can give a reliable time for its next update even before it can promise a resolution. The same escalation plan can guide a later case involving a returned gift or a change to an approved address. Giftpack guide to recipient support and escalation
Decide how the help desk will handle the case in which the person cannot use the old mailbox or the successor's portal. Give the agent an approved way to check identity and retrieve the original claim with limited access. Then test what happens if identity is still uncertain. The agent should be able to place the case on hold, name the team reviewing it, and provide a way to check back. In Maya's situation, the answer can be a shipping update once the warehouse confirms the parcel. For an unresolved claim, the employee can still get a useful update while the team protects the existing award from a mistaken transfer.
Keep the handoff useful without forwarding personal details
The transition meeting needs a count and a list of unresolved references. A warehouse arranging delivery may need a verified address. The help desk may need to know which vendor can confirm a selected order. Give each role the information it needs through the appropriate system, and plan when temporary access will end. Keep live claim links out of shared sheets and group messages. Anyone who can use a link to claim or redirect a gift may be able to act as its recipient.
A merger can bring earlier privacy promises with it. Federal Trade Commission staff addressed those promises in a 2014 letter about Facebook's proposed acquisition of WhatsApp. The letter concerned that transaction. For an employee gift program, give the privacy and legal owners the original notice, vendor terms, proposed recipient data fields, and intended use. They can assess which information the successor may handle and what needs further review before it moves. FTC announcement on the WhatsApp acquisition
The FTC's business security guide recommends inventorying information, limiting access, and setting retention. A program owner can apply those principles by keeping full delivery details in the fulfillment system and using case references in the cutover record. Close temporary exports and access after the transition, according to the organization's retention requirements. If a return or billing dispute remains open, assign a responsible person and keep the records that person still needs. FTC guide to protecting personal information
Tell employees about the change in a place they already trust. A post in the employee portal can explain which invitations remain valid, when support changes, and how someone without the old work email can reach help. A recipient can use a known website or phone number to verify a suspicious message, as the FTC advises. Make sure the known channel actually works before an email from a new domain sends people looking for it. FTC guidance on phishing messages
Close the program when someone can answer for every remaining gift
On Monday morning, Maya gets a response from the warehouse. The carrier took possession of the parcel on Friday. The old claim page had not caught up with the shipment record. She adds the verified tracking result to the original award and sends the employee to the approved tracking channel. Her decision on Friday kept the employee from getting a second invitation just as the first gift was on its way.
The merger team can now report 123 awards already fulfilled, 42 open invitations and 29 accepted selections with the old provider, one more dispatched order under lookup, and five unresolved cases. Each count has a date and an owner. The next weekly reconciliation will show which awards changed state and why. When the provider finishes the last authorized order, the team checks the final invoice and makes sure any remaining returns have a contact. Maya's program can close even though the new company portal went live weeks earlier.
At closeout, have finance link any shipping, replacement, or return charge to the same claim. An invoice can confirm that a charge was recorded. If an employee says the gift never arrived, support still needs the order and carrier evidence to investigate. Keep the outcomes and the remaining support assignments in the restricted program record before you remove temporary access. The person answering a question after the project team disbands should be able to recover the decision without searching a departed colleague's inbox.
Take that evidence into your next Giftpack program
If you're planning an employee milestone or onboarding program, Giftpack describes fixed gifts and eligible recipient choices. Bring the questions that mattered in Maya's case when you discuss the next program. Ask how your team can identify an award after an employee changes email addresses, what shipping evidence support can see, and how long the provider can help after the last claim date. For gifts already in progress, confirm the options for those specific claims with the current and prospective providers before changing any invitation. Giftpack employee gifts and recognition