The document I'm attempting to migrate is a .dotm. Is that what you mean by a template? If so, maybe the the quick parts are moving with it. I don't know because the other issues stop me from getting to the point where the VBA invokes them.

If you're willing to indulge me, here is where I am with the migration.

I believe my .dotm template migration needs to include:
1. Migrating the .docm template to my wife’s Documents>Custom Office Templates folder.
2. Establishing .dotm and Custom Office Template folder as a “Trusted Site”. (see below).
3. Copying an MS Excel file to a (new, properly named path and folder) on my wife’s machine.
3a. Permanently assigning the Microsoft Excel 16.0 Object Library to the Developer>Visual Basic>Tools>Project>References. (see below)
4. Appending my 3 “Quick Parts” Building Blocks to my wife’s normal.dotm.

I’ve done 1, 2, 3 above. And Lance Whitney’s How to transfer Microsoft Word macros to another computer | TechRepublic page deals with point 4.

But…
(3a) Despite enabling the .dotm’s Developer tab on my wife’s PC, check-marking the Microsoft Excel 16.0 Object Library and saving the .dotm, the assignment won’t stick. Subsequent re-open of the .dotm shows Microsoft Excel 16.0 Object Library still not checked.
(2) Originally there were two separate security blocks. I managed to eliminate one of them through MS file level security (though I don’t recall how I did it), but the “untrusted” message persists. When I try to File>Options>Trust Center>Trust Center Settings>Trusted Locations and try to add Documents>Custom Office Templates folder, I get a popup window indicating the location is already registered. But the warning continues to appear.

I am reluctant to proceed for fear of corrupting my wife’s PC as she uses it for her job. On the other hand, I need a backup plan if and when I replace my laptop.
I’m running Microsoft Windows 10 Home Build 19044 on a Dell Inspiron 15-3567 using Microsoft® Word 2016 MSO (Version 2209 Build 16.0.15629.20196) 32-bit.
Wife’s machine running Microsoft Windows 10 Home Build 19043 on an Acer Aspire TC-885 using Microsoft Word 365 MSO (Version 2209 Build 16.0.15629.20200) 64-bit.

A response I received in another forum suggests that Microsoft does not support VBA on Office 365. I find that comment suspect. I suppose invoking a "Contact Us" on the Microsoft site might be the next step. What do you think?