> ## Documentation Index > Fetch the complete documentation index at: https://docs.flowsign.app/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Flowsign is one word with a lowercase s. > The REST API base URL is https://my.flowsign.app and every endpoint lives under /api/v1. > When answering API questions, cite the HTTP method and endpoint path. > API access needs the Enterprise plan and an API key with the API access permission. # Migrate from PandaDoc > Move your templates, contacts and team from PandaDoc to Flowsign, step by step, and keep an archive of your completed documents. This guide moves your documents, templates, contacts and team from PandaDoc to Flowsign. There is no automatic importer: you re-upload your files and rebuild your templates, and completed documents stay behind as a downloaded archive. ## Before you start > [!WARNING] > > Check your renewal date first. PandaDoc annual plans renew automatically unless you give notice, commonly at least 30 days before the term ends. Confirm the notice period against your own order form. > [!WARNING] > > Download your archive before you downgrade. Content library items become inaccessible after a downgrade to the free plan, so download them first. ## What moves and what doesn't | Item | From PandaDoc | In Flowsign | | - | - | - | | Templates | Downloaded as PDF on all plans, or as Word on paid plans. Exports are flat files | Rebuilt by hand from the downloaded files | | Roles, fields and variables | Not in the export. Note them by hand | Roles and fields placed by hand, with merge fields for values that change per send | | Content library items | Downloaded as PDF only | Uploaded as documents where you still need them | | Completed documents | Downloaded as a ZIP from an emailed link | Not imported. Keep the downloaded archive | | Documents out for signature | Finish them, or void and resend | Sent again as new packages | | Contacts | Not self-service. Ask PandaDoc Support for a CSV | CSV import with column mapping | | Product catalogue | Exported to CSV from **Catalog > Export** | No quotes, pricing tables or catalogue. Keep the CSV for your records | | Bulk sends | Recipient lists you kept | Bulk send from a per-template CSV (Business and up) | | Branding | Your logo and brand colour | Logo and brand colour on emails (Business and up) | ## Steps **1. Take an inventory** List what your team uses in PandaDoc today, so nothing is missed on the way out: * Templates * Pricing tables and catalogue * Payments * Forms * Approvals * Bulk send * CRM integrations * Webhooks or API For each item, note who owns it and how often it is used. Flowsign has no quotes, pricing tables or catalogue, and may not have a match for every other item, so check the list against these docs, or [ask us](/support/contact.md), before you set a switch date. **2. Download your templates** Templates and documents download as PDF on every PandaDoc plan. On paid plans you can also choose **File > Download > Microsoft Word**. The exports are flat files, so the roles, fields and variables do not come with them. For each template, write down its roles, the signing order, which fields each role completes, and every variable it uses. **3. Download your content library** Content library items download as PDF only. Download the ones you still need now, because they become inaccessible after a downgrade to the free plan. **4. Download your completed documents** Select the completed documents and choose **Download**. PandaDoc emails you a link to a ZIP, and the link expires within a week. Batches of 200 to 300 documents are recommended. Attachments and files collected from recipients are not in the ZIP, so download those separately where you need them. > [!NOTE] > > Signed documents from another platform cannot be imported into Flowsign with their audit trail or certificate. Store the downloaded archive somewhere safe and treat it as your record. **5. Ask for your contacts and export your catalogue** Contacts export is not self-service in PandaDoc. Ask PandaDoc Support for a CSV of your contacts, and allow time for the reply. For Flowsign, the file needs a column each for name, email, phone, job title, company and tags, and every row needs a name and a valid email. If you use the product catalogue, export it to CSV from **Catalog > Export**. This file is for your records only. **6. Finish the documents still out for signature** Documents in progress do not move. Let them finish in PandaDoc, or void them and resend them from Flowsign once your templates are ready. **7. Set up your Flowsign organisation** Follow [Setting up your organisation](/guides/organisation-setup.md) for the full order. The parts that matter most for a move: * **Branding (Business and up).** Add your logo and brand colour in [Branding](/guides/settings/branding.md) so your emails look familiar to recipients from day one. * **Members.** Invite each person in [Members](/guides/settings/members.md), one at a time, with a role. See [Roles & Permissions](/guides/settings/roles-and-permissions.md). * **SSO and provisioning (Enterprise).** Set up single sign-on and SCIM provisioning in [Organisation security](/guides/settings/security.md). **8. Import your contacts** In [Contacts](/guides/contacts/contacts.md#importing-contacts), choose **Import** from the **More actions** menu, pick your CSV and check the column mapping. Rows without a name and a valid email are skipped. **9. Rebuild your templates** For each template, create a new one and upload the downloaded files. Flowsign accepts PDF, Word, Excel, PowerPoint and images, and converts anything that is not a PDF to one. See [Document types](/document-types.md) and [Building a workflow](/guides/building-a-workflow.md). Add your roles and signing order, then place the fields in the [template field editor](/guides/templates/template-fields.md): * **Fillable PDFs.** If the PDF has real form fields, the field editor shows **Import form fields** with a review step. You still assign each field to a role by hand. See [Field editor](/guides/packages/fields-editor.md). * **Flat PDFs.** Place each field by hand. Expect this for PandaDoc exports. The field types are signature, initials, date signed, name, email, company, title, text, number, checkbox, radio, dropdown and merge field. Use merge fields where the PandaDoc template used variables. See [Merge fields on PDFs](/guides/templates/merge-fields-on-pdfs.md). Set reminders and expiry on the template, then publish it. > [!TIP] > > Start with the two or three templates your team sends most. The rest can follow once the first ones are in use. **10. Recreate your bulk sends (Business and up)** A bulk send in Flowsign runs from a template, with a CSV of recipients for that template. See [Bulk send from a template](/guides/bulk-send/create-bulk-send.md). If answers decide which documents go out or who signs, build that as a workflow (Business and up). See [Workflow signing](/guides/building-a-workflow.md#workflow-signing). **11. Send a test package** Send each rebuilt template to yourself and a colleague before the team relies on it. Check the email, the signing order and every field. [Getting started](/getting-started.md) covers a first send from start to finish. ## After you switch * Tell your team the date new documents start going out from Flowsign, and point them to [Getting started](/getting-started.md). * Confirm every document left in PandaDoc has finished or been voided. * Check that your downloaded archive opens, and that you have the attachments and collected files that were not in the ZIP. * Give PandaDoc notice before the date on your order form, so the plan does not renew. ## Need a hand? The Enterprise plan includes hands-on migration: the Flowsign team rebuilds your templates and sets up your workspace with you. [Contact support](/support/contact.md) to talk it through. ## Related * [Setting up your organisation](/guides/organisation-setup.md) * [Building a workflow](/guides/building-a-workflow.md) * [Contacts](/guides/contacts/contacts.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.