Completed PDF archive
Generate the signed PDF with ApproveMe Save as PDF and store it once in WPsigner SecureStorage.
WPsigner addon · Version 1.2.0
Move signed ApproveMe documents to WPsigner without leaving WordPress
Archive completed WP E-Signature / ApproveMe documents in WPsigner on the same WordPress site. The importer runs in the background, skips duplicates, preserves the original ApproveMe data, and keeps document processing on your server.
Imports signed documents only. Templates, drafts, and active signing workflows are not migrated.
ApproveMe Import
Background archive migration
800
Signed
125
Already imported
675
Remaining
Documents per batch5
Start background import
Safe to close this tab — progress continues via WP-Cron.
100%
processed on your WordPress server
SHA-256
hash stored for every imported PDF
Background
pause, resume, and retry failed items
Duplicate-safe
previously imported documents are skipped
What the importer brings into WPsigner
Each signed ApproveMe document becomes a completed, searchable archive record in WPsigner.
Document title and completion date
Carry over the ApproveMe title and the latest signing date so archives remain easy to identify.
Signer records
Import valid signer names, email addresses, signing order, signed status, and signing dates.
Audit history
Add the import event, original ApproveMe document ID, checksum, PDF engine, and up to 50 source events to the WPsigner audit log.
SHA-256 document hash
Calculate and store a cryptographic fingerprint for the archived PDF.
Automatic migration tag
Label every imported record “Imported from ApproveMe” for fast filtering and review.
Archive migration — not a blind 1:1 conversion
The addon is deliberately focused on completed legal archives. These items still need a manual decision or recreation in WPsigner.
- Draft, awaiting, trashed, and unsigned documents
- ApproveMe templates and reusable field layouts
- Active signing workflows, reminders, and routing rules
- ApproveMe settings, custom fields, and product configuration
- Separate ApproveMe certificate or audit-trail PDF files
- Cross-site migration between different WordPress installations
Built for safe, resumable migrations
Large archives need more than a one-click request. WPsigner ApproveMe Importer uses a controlled queue with clear progress and recovery tools.
ApproveMe stays untouched
The importer only reads ApproveMe tables. It does not update, delete, or deactivate your source documents.
Duplicate detection
A persistent document map prevents the same ApproveMe record from being imported twice.
Background processing
WP-Cron continues the queue after you leave the page; an open admin tab simply accelerates progress via local AJAX.
Pause and resume
Stop the queue when needed and continue later without restarting completed work.
Retry failed documents
Requeue only failed IDs after correcting a PDF, memory, or server issue.
Protected admin actions
WordPress capability checks, AJAX nonces, sanitized inputs, and local processing protect the migration workflow.
How to import signed ApproveMe documents
Keep WP E-Signature and its Save as PDF addon active until the queue finishes.
- 1
Install WPsigner on the same site
Activate WPsigner alongside your existing ApproveMe installation. This importer does not transfer records between separate WordPress sites.
- 2
Keep ApproveMe Save as PDF active
The addon uses ApproveMe’s native PDF engine to preserve the original signed-PDF design.
- 3
Open WPsigner → ApproveMe Import
Review counts for signed, awaiting, draft, already imported, and remaining documents before starting.
- 4
Choose a batch size and start
Select 3, 5, 8, or 10 documents per batch based on server capacity, then start the background queue.
- 5
Monitor, retry, and verify
Track imported, skipped, and failed documents; retry failures and verify the tagged records in WPsigner.
Requirements and important limits
Check these points before starting a production archive migration.
Required
- WordPress 5.8+ and PHP 7.4+
- WPsigner active on the same WordPress installation
- WP E-Signature / ApproveMe available during migration
- ApproveMe Save as PDF addon active until completion
Know before you import
- There is no dry-run mode or global rollback; back up WordPress first.
- Only documents with ApproveMe status “signed” are queued.
- A native PDF keeps the ApproveMe design; per-document fallback PDFs can look different.
- Valid signer email addresses are required to create signer records.
- Low-traffic sites may process WP-Cron queues more slowly unless a real cron job is configured.
Designed for real archives
Leave the queue running while you keep working
The importer processes controlled batches instead of trying to load an entire archive in one request. As a practical reference, about 800 documents may take 30–90 minutes depending on server load, PDF complexity, and cron frequency.
- Live progress, ETA, imported, skipped, and failed counters
- Recommended default: 5 documents per batch
- Safe to close the browser tab while WP-Cron continues
Still deciding between ApproveMe and WPsigner?
Review the full pricing, security, integrations, and migration comparison before moving your archive.
ApproveMe Importer FAQ
What does WPsigner ApproveMe Importer import? +
It imports signed ApproveMe documents as completed PDFs in WPsigner on the same WordPress site. It also carries over titles, completion dates, valid signer records, a SHA-256 PDF hash, an import audit event, and up to 50 ApproveMe events.
Does it import pending documents or templates? +
No. It is an archive importer for documents whose ApproveMe status is signed. Drafts, awaiting documents, templates, fields, and active workflows should be recreated or re-sent from WPsigner.
Will the importer modify or delete my ApproveMe documents? +
No. The importer reads the source tables and leaves ApproveMe records intact. It does not deactivate ApproveMe automatically. A normal WordPress backup is still recommended before any production migration.
Can I run the import again safely? +
Yes. The importer keeps a map between ApproveMe and WPsigner document IDs and automatically skips documents already imported. You can pause, resume, and retry failed items.
Do documents leave my WordPress server? +
No. Database reading, PDF generation, hashing, and WPsigner storage happen locally on your WordPress installation. The migration does not upload document content to WPsigner servers.
Will imported PDFs look exactly like ApproveMe? +
The importer uses the active ApproveMe Save as PDF addon to generate the native PDF design. If that engine fails for an individual document, a TCPDF fallback can archive it, but its design may differ.
Can it migrate documents to another WordPress site? +
No. Version 1.2.0 imports from ApproveMe into WPsigner on the same WordPress installation. It is not an export/import package for cross-site transfers.
How long does a large import take? +
It depends on hosting resources, PDF complexity, batch size, and WP-Cron frequency. As a practical estimate shown by the addon, approximately 800 documents may take 30–90 minutes.