Note:Don't know which Editor version you are using? Find it out here.
- Why did we build Editor 2.0 as a separate editor?
- I like the Classic Editor. Why do I have to migrate?
- How long will it take to migrate?
- Is there a pricing difference between the Classic Editor and Editor 2.0? Or a cost to migrate?
- What happens to your Classic Editor templates and documents
- How will this affect my current workflow?
Why did we build Editor 2.0 as a separate editor?
We rebuilt our editor from the ground up to give you and your customers a better PandaDoc experience. Editor 2.0’s powerful features and functionality are specifically designed to streamline your document workflow.
I like the Classic Editor. Why do I have to migrate?
Compared to the Classic Editor you’re familiar with, Editor 2.0 offers a more modern, responsive editing environment that makes creating documents in PandaDoc smoother, faster, and simply more enjoyable. All new PandaDoc features are now only released in Editor 2.0, and after June 30, 2021, we’ll offer only non-bug-fix support via chat to users of the Classic Editor.
Although PandaDoc’s Classic Editor and Editor 2.0 are both PandaDoc, they are entirely separate platforms. This means your current documents, templates, and content library items are incompatible with Editor 2.0.
But fear not! Your Classic Editor documents won’t be altered and will remain accessible – even after your account is moved over to Editor 2.0. Any outstanding documents awaiting signature or payment will be unaffected and can be completed as usual.
Read more in this Unleashed article.
How long will it take to migrate?
Giving you access to Editor 2.0 is as easy as flipping a switch. However, the content you’ve already created will be incompatible, so you’ll need to work with your CSM to establish a migration timeline for your team.
A rough estimate of migration ranges from 1-4 weeks. If you’re a small to medium business, count on 2 weeks; Enterprise clients take longer, sometimes up to 4 weeks. The exact time frame depends on the number of templates, as well as training schedules. We’ll work with you to ensure your business operations are not interrupted.
Is there a pricing difference between the Classic Editor and Editor 2.0? Or a cost to migrate?
For those on our current pricing, there is no additional cost to upgrade to Editor 2.0! If you’ve been on a contract with a legacy pricing plan, you’ll need to talk to your CSM about any changes to your pricing. Our migration onboarding package starts at $750.
What happens to your Classic Editor templates and documents
What will happen to my Classic Editor templates after we complete the switch?
All your Classic Editor templates will be switched to Editor 2.0 so you can take advantage of its updated functionality and features. Your Classic Editor templates will no longer be available on-demand, or even visible in your templates list. However, we’ll still keep them if you need to access them at a later date. Talk with your CSM about our content conversion options if you think you’ll need a hand.
After I migrate, will I still be able to access my Classic Editor documents?
Yes — all your Classic Editor documents, regardless of statuses (draft, viewed, completed, etc.) will still be accessible and available for download and other basic actions.
What happens to documents that have been sent and viewed, but are incomplete?
These will continue to be available — they’ll simply open in the Classic Editor. Any outstanding documents awaiting signature or payment will be unaffected and can be completed as usual.
What will happen to completed and draft documents in the Classic Editor if a user tries to edit them?
Users will still be able to view completed documents and daft documents in the Classic Editor. Also, all documents in draft status will be available for editing, as well as other actions like sending and completing. Please note, in the future we will eventually end draft documents in the Classic Editor and therefore we encourage you to migrate these draft documents as well.
Is there any content that can not be migrated?
Shared content (including shared folders, templates and content library items) can not be migrated. The original source of the content can be migrated though. Therefore, we will need the original link to migrate it and then it would need to be reshared again after your migration is complete. Our engineering team is working hard to facilitate this process.
How will this affect my current workflow?
How will this change affect my team? Will I need to retrain my users?
Editor 2.0’s layout is different from the Classic Editor, but the overall Template > Document > Client workflow should remain intact for end users. Our Help Center is filled with step-by-step guides to make the transition smooth and simple. Furthermore, our Customer Success team is ready to work with you to determine the best path for training, if necessary.
Can I have access to both Classic Editor & Editor 2.0?
Yes! To allow a transition period for your team, we can switch you to Editor 2.0 and continue to keep the Classic Editor available, so you can have access to both. You’ll be able to tell which documents and templates are within Editor 2.0 — just look for “2.0” next to its title. Note that before creating a new document or template in Editor 2.0, you’ll need to select the appropriate option from within the dropdown menu.
How will my existing integrations be affected?
For the majority of users, integrations will be unaffected. However, exceptions do exist, so if you’re using integrations, please ask your CSM whether any of your integrations will be affected by the transition.
I’ve switched over to Editor 2.0, but I’m missing some of the Classic Editor’s functionality?
We hope to fully match Editor 2.0’s feature set to that of the Classic Editor by spring 2021.
Is there an option to disable creating any new templates using the Classic Editor but still be able to use existing ones?