Nobody switches document systems for fun. You switch because the old one costs too much, stopped being supported, or never did what you needed. Then you open the templates folder and find sixty files, half of which nobody has touched since 2019.
The good news is that most of the work is sorting, not rebuilding. A DocFusion template is a Word document with fields and rules marked inside it. The Word document is the part worth keeping, and it travels.
Start with an inventory
Before you move anything, list your templates and mark the ones you actually used in the last six months. Most businesses find a small core of quotes, invoices, contracts and letters that do nearly all the work, and a long tail of old versions and one-offs.
Move the core. Archive the tail. A template nobody has opened in two years doesn't need migrating. It needs deleting, or at most saving somewhere in case someone asks.
Find the original Word files
You need the template files, not documents DocFusion made from them. A finished quote has the fields already filled in, so the rules are gone. Look for the .docx files that still show the field markers.
If several versions of the same template exist, find out which one is live before you move it. Moving the wrong version is a quiet mistake. It only shows up when a customer gets last year's terms.
Know what should come across
Fields, repeating sections for line items, and conditions that show or hide a paragraph are the heart of a DocFusion template, and those are what an import should keep.
Drawn objects are the weak spot. Text boxes, charts and SmartArt sit on top of the page rather than in the flow of the text, so fields inside them may not be read and their layout can move. If your template keeps the client's address in a text box, move it into an ordinary paragraph or a table cell before you import. It's ten minutes of work that saves an afternoon of puzzling.
Read the report, then test with real data
After an import, look at what was recognised and what wasn't. Then fill the template with data from a real, recent job and put the result next to the document DocFusion made for the same job.
Check the amounts and dates first, because format differences show up there. Then check every optional section, both with and without the condition that shows it. Then check a line-item table with one row and with twenty. A template that passes those three checks is ready for customers.
Run both systems for a short while
Don't switch everything over on one day. Move the templates you use most, use them for real for a week or two, and keep DocFusion running in the background for anything that comes up. Switch each old template off once its replacement has made real documents without trouble.
This is slower than a big-bang cutover. It's also the version where nobody sends a broken quote to your biggest client on a Monday morning.
How it works in E·BIZI Papers
E·BIZI Papers reads DocFusion templates directly. Upload the Word file (up to 25 MB), and Papers recognises the DocFusion fields, repeating sections and conditions, and builds sample data so you can see a filled document straight away. Images and logos go into your asset library, so the next template can reuse them.
Papers keeps an import report with the template that lists anything it couldn't carry across, so you can fix those before the template goes live. Upload, read the report, test with real data, then publish.