Proving the Migration Path: A Records Management Software Pilot Across Legacy Systems.

About the Client

Created in 1961 by a special act of the Florida Legislature and headquartered in Brooksville, SWFWMD is one of five regional agencies directed by Florida law to protect and preserve the state’s water resources. Governed by a 13-member unpaid Governing Board appointed by the Governor, the District encompasses roughly 10,000 square miles across all or part of 16 counties in west-central Florida, serving a population of nearly six million people.

Industry Context

For government agencies migrating decades of legacy records into a new ECM/RM platform, attempting a full migration all at once carries real risk: unknown data quality issues, unclear effort estimates, and potential disruption to ongoing operations if problems surface only after the fact. Piloting migration on a small, real subset of records before committing to full-scale migration is standard practice in enterprise systems implementations. It lets an organization surface data mapping issues and validate its tooling before scaling up — particularly valuable for a public agency that needs defensible cost and effort estimates to bring back to its governing board. Because the Vignette ECM/RM suite, later absorbed into OpenText’s ECM Suite, included many interlocking modules, standing up and testing the full technical stack across both acceptance and production environments was itself a meaningful undertaking before any pilot data could move.

Current Situation

Iknow was selected by the District to design, install, and configure a scalable ECM and RM solution. In a previous assignment for the District, Iknow developed the ECM/RM strategy and implementation roadmap; in this assignment, Iknow began the implementation, with an objective of deploying the software in two technical environments, implementing the records management file plan, and conducting an initial pilot.

• No platform installed and validated yet. The District needed the Vignette ECM/RM platform installed, configured, and tested across two full technical environments before any real records could move.
• No proven data migration process. No proven process existed for mapping and migrating the District’s records from its many legacy systems into the new platform.
• No grounded estimate for full-scale migration. The District needed credible, grounded estimates of the effort and resources a full legacy migration would require, not rough guesses.
• No defined approach to validating migrated data. Any migrated data needed a rigorous way to be tested and validated, with a defined path for resolving failures, before the District could trust the new system with its real records.

• Install, configure, and test the core Vignette ECM components and related products in the District’s acceptance and production environments.
• Implement the District’s records management file plan into the Vignette solution.
• Conduct a pilot migration of a small subset of records to validate the migration approach and estimate the effort required for full migration.
• Create a test plan and test cases to validate migrated data, and transfer knowledge to the District’s IT staff.

How Iknow Structured the Work

Iknow structured the engagement in four parts performed in series — platform installation, a records management pilot, test plan and test case development, and knowledge transfer — reflecting Iknow’s systems integration and data migration methodology for validating a migration approach on real data before committing to full-scale execution.

Key Activities & Decisions

• Core platform installation. Iknow worked with the District’s IT staff to install, configure, and test the core Vignette ECM components — Content Management, Records Management, Portal, and Collaboration — in the District’s acceptance and production environments.
• Related product installation. Iknow also helped install, configure, and test several related products, including Vignette Builder, Collaborative Publishing and Authoring, and Collaborative Documents and Records Management System.
• Records management pilot. Iknow conducted a records management pilot, implementing the District’s file plan into the Vignette solution, defining and documenting the processes for mapping and migrating data, and moving a small subset of records.
• Full-migration effort estimation. Iknow used the pilot to estimate the level of effort and resources it would take to fully migrate all available data from the District’s legacy systems into the Vignette solution.
• Test plan and validation methodology. Iknow created a test plan and test cases for testing and validating the migrated data, along with a methodology for resolving failed tests.
• Knowledge transfer and training. Iknow delivered knowledge transfer to the District’s IT staff through classroom-based training and written instruction manuals.

Stakeholders & Collaboration

Iknow served as prime contractor, working directly with the District’s IT staff throughout platform installation, the migration pilot, test development, and knowledge transfer.

Standing Up a Complex, Multi-Module Platform Without Disrupting Operations

The Vignette ECM/RM suite spanned numerous interlocking modules, and installing that full technical stack across two environments risked real disruption if done carelessly against a District still relying on its legacy systems day to day. Iknow addressed this by working directly alongside the District’s own IT staff to install, configure, and test each component systematically in acceptance before production, rather than deploying everything at once.

Committing to a Full Legacy Migration Without Knowing the Real Effort Involved

Attempting a full-scale migration of decades of legacy records without first understanding the effort and risk involved could have exposed the District to significant cost overruns or data problems. Iknow addressed this by scoping a genuine pilot — implementing the real file plan, migrating an actual subset of records, and using that hands-on experience to produce grounded effort and resource estimates rather than speculative ones.

Quantitative Outcomes

• Platform scope delivered: Four core Vignette modules installed, configured, and tested across two technical environments (acceptance and production).
• Related products delivered: Three additional related products installed, configured, and tested.
• Migration pilot completed: A pilot migration successfully moving a subset of records from legacy systems into the new platform.
• Validation framework delivered: A complete test plan and set of test cases developed for validating migrated data.
• Engagement duration: Three-month assignment.

Qualitative Outcomes

SWFWMD had the Vignette ECM and records management software installed, configured, and tested on its infrastructure, and had successfully demonstrated the migration of records from legacy systems to the new records management platform. The District also had the resource estimates it needed to plan the entire RM migration to the new solution — genuine evidence that the pilot delivered both a working technical proof point and the planning information needed to responsibly scope a full-scale migration.

Timeline to Impact

Within the three-month engagement, Iknow moved the District from an approved strategy and roadmap to a working, tested platform installation and a successfully piloted migration, giving the District everything it needed to plan and budget for full-scale legacy data migration.

Core Skills

• Enterprise content management platform implementation
• Legacy data migration planning and piloting
• Records management file plan implementation
• IT knowledge transfer and training

Methods & Frameworks

• Phased environment deployment (acceptance then production)
• Pilot-based migration validation
• Test plan and test case development

Technologies & Tools

• Vignette ECM/RM suite: Content Management, Records Management, Portal, Collaboration
• Vignette Builder, Collaborative Publishing and Authoring, and Collaborative Documents and Records Management System (now part of OpenText’s ECM Suite)