Skip to main content

How do I migrate documents from a shared drive or legacy ECM?

Plan a migration that preserves files, identifiers, metadata, access intent, and required history, then validate it with a representative pilot. FormKiQ provides document APIs and licensed CLI tooling for bulk import and metadata mapping. A file copy alone does not migrate governance or workflow semantics. Reconcile counts, content, permissions, and exceptions before cutover.

Define what must survive​

Inventory source documents, versions, paths, identifiers, metadata fields, links, access rules, holds, and retention requirements. Decide which historical material must remain accessible and how references from other business systems will resolve after cutover.

Map source identifiers to stable destination attributes and preserve a source-to-document/site manifest. Normalize data with approved preprocessing where needed. Choose APIs or the licensed FormKiQ CLI for the workload; AWS CLI availability does not imply FormKiQ CLI entitlement.

Pilot before scaling​

Import a small collection containing large files, duplicates, restricted records, bad metadata, and unusual formats. Check content hashes or equivalent integrity evidence, record counts, field values, effective access, and required governance state. Reconcile uncertain retries before creating a second record.

Control concurrency and decide which OCR/indexing actions should run during migration. Plan a final delta, exception sign-off, rollback/archive access, and source retirement. Keep the migration manifest and verification evidence in an approved location.

Edition and configuration​

APIs are available across editions. FormKiQ CLI and separately scoped migration/professional services are Advanced/Enterprise offerings; confirm tools, modules, source access, and implementation scope.

Continue with the detailed guides​

Privacy settings

Analytics is optional. Your analytics choice is shared with formkiq.com and remembered for up to six months. Change it here at any time.

Essential preferences and search

We remember your privacy choice and display preferences. Search runs in your browser using Pagefind files hosted with the docs. It works whether you accept or reject analytics.

Measure page views and installation-link clicks. This does not enable advertising on the docs. Existing marketing choices for the main website are kept unchanged.

Read the docs privacy notice or manage other main-website privacy choices.