Migrate from Alfresco to FormKiQ

Plan an Alfresco migration to FormKiQ with source mapping, document and version validation, access tests, staged cutover, and clear archive acceptance criteria.

Migrate from Alfresco by defining the target workflow, mapping source records and permissions, piloting a representative collection, and reconciling the result before switching applications. Moving file bytes is one part of the project; versions, business references, access rules, and ongoing obligations need their own acceptance evidence.

FormKiQ supports API-based imports and, for entitled commercial deployments, CLI migration tools. Your migration scope defines the Alfresco extraction method, transformation rules, import process, and validation. An Alfresco-specific conversion utility or automatic workflow translation is not assumed.

Inspect a source-to-target mapping example

Choose the destination before the extraction method

For historical files, Legacy System Archive and Access delivers the archive application, including mapped source context, reconciliation and acceptance, retrieval, and continuing governance. For current work, select the appropriate Business Solution or integrate document services into the application that will continue the process.

Inventory the Alfresco edition and version, custom content model, extensions, storage arrangement, integrations, and export access. Its public REST interfaces and version-history API are documented extraction interfaces to assess against your installed version. Copying a raw content store alone does not reconstruct repository metadata or permissions.

Map the meaning of the repository

Alfresco migration design and acceptance evidence
Source concernTarget designEvidence to retain
Node identity and business linksPreserve the original reference alongside the FormKiQ document ID and business record.A source-to-target ledger and successful retrieval from each dependent application.
Types, aspects, and custom propertiesMap selected fields to attributes, classifications, schemas, and relationships according to their business meaning.Field definitions, value transformations, required-field checks, and recorded exceptions.
Folders and permissionsDesign sites, paths, groups, and any narrower folder or attribute-based restrictions.Access tests for permitted, denied, and revoked users. Similar path names do not prove equivalent permissions.
Content and versionsDecide which revisions must move and how source revision labels, dates, authors, and binaries remain attributable.Counts by document and revision, integrity checks, and historical-version retrieval tests.
Retention, holds, and audit historyMap continuing obligations; retain required source history as evidence and configure target controls.Approved policy mappings, hold tests, preserved history exports, and authorised acceptance. A new target audit trail does not recreate past events.
Workflows and connected systemsConfigure the target application process and update integrations; decide how open work transitions.Representative end-to-end tests, in-flight case reconciliation, and agreed reference-switch behaviour.

Illustrative mapping · fictional identifiers and results

Keep a historical order connected to its documents

Source file

Order: ORD-1042
Alfresco node: sample-node-42
Property: sample:orderReference = ORD-1042
Revision: 2.1
Access: purchasing reviewers

Accepted target file

Archive dossier: ARC-1042
FormKiQ document: sample-document-73
Original node, order reference, and revision recorded in the migration mapping.
Mapped reviewer access tested before acceptance.

The source-to-target ledger records import state and validation outcome. If the content succeeds but a required reference fails validation, keep that item in the exception queue and withhold acceptance. Retry the failed stage using the existing mapping so the job does not create a duplicate.

The archive workflow example shows mapping, inspection, exception resolution, acceptance, and later retrieval. The organisation's source fields and access rules are configured for its archive.

Run the move in controllable stages

  1. 1 · Pilot

    Include the difficult cases

    Test representative documents, restricted folders, multiple versions, unusual metadata, and an open workflow. Verify the target application and access model before increasing volume.

  2. 2 · Import

    Use repeatable batches

    Track extraction, transformation, upload, processing, and validation separately. Record source IDs and import state, bound retries, and monitor source and target limits.

  3. 3 · Cut over

    Reconcile before switching

    Apply the agreed source-write freeze or delta strategy, validate changes since the bulk load, and switch application references. Keep a recoverable source through the agreed rollback window.

The FormKiQ migration guide describes API, CLI/CSV, staging, and external-reference patterns. The edition and licensing guide identifies commercial CLI entitlement. Choose a tested import pattern rather than assuming every migration tool is included in Core.

What the RGF example establishes

RGF Staffing Belgium's published account describes a migration of more than 20 million documents, using staged AWS processing, metadata preparation, FormKiQ API imports, and application-reference updates. That customer-specific approach is evidence to study, not a universal recipe for every Alfresco installation.

RGF migration snapshot · Original customer account

Migration acceptance checklist

  • Reconcile documents, required revisions, failures, and intentional exclusions against the source manifest.
  • Verify content integrity with the agreed full-set or sampling method and document its limits.
  • Check metadata values, original references, search results, and application retrieval links.
  • Test permitted and denied access, legal holds, retention handling, and open-work transitions.
  • Confirm asynchronous processing and indexing have completed where required for cutover.
  • Exercise rollback, including how changes made in the target would be reconciled.
  • Obtain business and operations acceptance before source retirement and temporary-data cleanup.

Accept the usable repository, not just the upload

The migration is ready when users can retrieve the right records, permissions and obligations work as agreed, and dependent applications use the validated references. Keep that acceptance decision separate from the completion of a bulk transfer.

Evaluate FormKiQ as an Alfresco alternative · Broader legacy ECM migration guidance

Scope one Alfresco migration pilot

Bring the installed version, a representative collection, its metadata and permissions, and the applications that reference it. We can review extraction, application fit, validation, and cutover boundaries.

Book a migration review

Start with FormKiQ Core

The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

Get Started Free

Deploy FormKiQ Essentials or Advanced

Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

Explore Options

Plan an Enterprise Rollout

For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

Book a Call