MoveRight is the moving company CRM that generates your estimates, quotes, and contracts without you touching a Word doc. For the last year, most of those documents came out of PandaDoc. We’ve been replacing it with AegisDoc — our own engine, built for moving workflows. The migration is far enough along that it needs a control panel. This is what shipped: a new /business/documents settings page that shows you where your documents are coming from and lets you switch engines without a support ticket.
What the Page Shows
Open /business/documents and you get a per-document-type report. Each row is a document type — Estimate, Quote, Contract, Change Order, Addendum — and the columns tell you how many of each have been generated, broken down by engine.
| Column | What it means |
|---|---|
| Document Type | The canonical type (Estimate, Quote, Contract, etc.) — now classified by a single system across the app |
| Aegis Count | Documents generated by the AegisDoc engine |
| PandaDoc Count | Documents still on the legacy PandaDoc engine |
| Active Engine | Which engine this document type is currently set to use |
| Template URL | The template location for the active engine — editable inline |
| Swap | One-click control to switch the active engine for this type |
No exports, no SQL, no asking engineering to run a report. The numbers are right there.
Why We Built It
The migration from PandaDoc to AegisDoc has been rolling out document type by document type. Until now, the only way to know how far along it was — how many of your estimates were coming from AegisDoc versus PandaDoc — was to file a ticket and wait.
That’s not a reasonable status quo for a migration that touches every quote you send. Admins needed visibility. The /business/documents page puts the migration report in the admin’s hands. You can see which document types have flipped, which haven’t, and how many documents each engine has produced. You don’t need a status meeting to know where things stand.
The report is backed by new database indexes, so it loads fast even on accounts with tens of thousands of generated documents.
How to Swap Engines
Each row has a Swap control. Click it. The active engine for that document type changes. That’s the whole interaction.
- Zero data loss. Existing documents stay where they are — PandaDoc documents don’t move to AegisDoc, and vice versa. The swap only affects new documents going forward.
- Zero risk. Swapping doesn’t delete anything. If the new engine doesn’t behave the way you expect, swap back. One click each way.
- Per type. You can run Estimates on AegisDoc and Contracts on PandaDoc if you want to phase the migration gradually. Most accounts flip one type, watch it for a week, then flip the next.
This is the migration tool we should have shipped at the start. It’s here now.
Template URL Editing
Each document type has a Template URL field — editable inline on the same page. The template is what AegisDoc uses to produce the final document: the layout, the fields, the MoveRight-branded styling, the terms and conditions block.
If you’ve customized a template — added your company logo, changed the payment terms language, restructured the line-item table — you update the URL here and every new document of that type picks it up. No re-deploy, no engineering ticket.
For accounts still on PandaDoc, the PandaDoc template ID stays in place until you swap. Once you swap to AegisDoc, the AegisDoc template URL takes over.
One Small Bonus
The Estimate template now displays the job timeline for unscheduled moving events. If a customer has an estimate for a move that hasn’t been scheduled yet, the estimate shows the proposed timeline block — pickup window, delivery window, padding days — so the customer can see what they’re agreeing to before the dates are locked. This was a gap in the previous template; it’s closed.
Already on MoveRight? Go to /business/documents, check your counts, and swap the document types you’re ready to move. Not on MoveRight yet? AegisDoc is what document generation looks like when it’s built for movers, not bolted on.
References: