30 lines
1.6 KiB
Markdown
30 lines
1.6 KiB
Markdown
# adobe-to-docusign-migrator
|
|
|
|
## Project Purpose
|
|
A migration toolkit/agent that automates extraction of Adobe Sign library templates (PDFs, fields, roles, workflow), transforms them to DocuSign template model, and creates/imports them into DocuSign.
|
|
|
|
## Background
|
|
- Adobe Sign and DocuSign both expose APIs to manage templates, fields, recipients, logic, and documents.
|
|
- Adobe Sign (Acrobat Sign) uses "library documents" as templates, with data accessible via JSON API calls (but not exportable in a single file). You assemble the template info by calling:
|
|
- `/libraryDocuments/{libraryDocumentId}` (metadata, PDFs, roles)
|
|
- `/libraryDocuments/{libraryDocumentId}/formFields` (fields/tags)
|
|
- `/libraryDocuments/{libraryDocumentId}/recipients` (recipients)
|
|
- `/libraryDocuments/{libraryDocumentId}/workflows` (if applicable)
|
|
- `/libraryDocuments/{libraryDocumentId}/auditTrail` (audit log, rarely needed for migration)
|
|
- DocuSign templates are more easily exported as a single payload, but you can also build them incrementally over the API.
|
|
- The most complex part of migration is mapping logic/fields/roles that are not 1:1 matches (conditional fields, complex routing).
|
|
|
|
## API Output Samples
|
|
See `api-samples.md` for category-by-category JSON breakdowns.
|
|
|
|
## Next Steps
|
|
- Add full agent harness scaffold (`docs/agent-harness/` structure, project README, spec templates)
|
|
- Collect sample real-world Adobe Sign template JSONs
|
|
- Define mapping/transforms for fields, roles, logic
|
|
- Write initial extraction + mapping scripts
|
|
- Draft Product Spec
|
|
|
|
---
|
|
|
|
*Created: 2026-04-14*
|
|
*scaffolded by Cleo* |