Microsoft 365 Data Migration Project

Statement of Work Microsoft 365 Project 1. Background Strategic Weapons Facility Pacific (SWFPAC) currently supports a legacy Microsoft Access 2003 database identified as mission-critical and in need of immediate migration. This system serves as a warehouse and inventory management solution tracking defined storage locations, personnel assignments, and two distinct categories of inventory. SWFPAC requires professional services to facilitate the migration of mission-critical data from the Access legacy database to Flank Speed, ensuring compatibility and interoperability with the Navy enterprise with minimal disruption to SWFPAC operations. 2. Scope of Work The vendor shall provide all necessary personnel, expertise, and services to design and build an application compatible with the Navy s Microsoft 365 platform (often referred to ask Flank Speed ) to facilitate the migration of data from an existing Microsoft Access 2003 database to Flank Speed. The final product will utilize SharePoint Online (SPO) as the primary data repository and Microsoft Power Platform (Power Apps and Power Automate) for user interfaces, relational workflows, and automated document generation. 2.1 Vendor Competency Requirements Interested vendors must provide documented evidence of successful past performance and technical competency in designing, deploying, and supporting migrations from legacy Microsoft Access systems to Microsoft 365/Power Platform environments. 2.2 Data Architecture, Test Environment, & Migration Support Due to data security protocols, the vendor will not be provided access to live data. Instead of dictating a rigid target architecture, the Government requires the vendor to evaluate the legacy Access 2003 database structure and propose an optimized target architecture. The vendor s proposed data schema must successfully manage and relate the following core situational entities (encompassing datasets that range from <500 up to 3,000 records): Warehouse Locations (Racks/Lockers) Defined physical locations that can be assigned inventory, and subsequently assigned/issued to specific personnel. Personnel Assignments Tracking individuals assigned to specific racks, lockers, or individual pieces of equipment (handling check-in, check-out, and return states). General Gear Inventory Non-serialized bulk items categorized and inventoried by aggregates (tracking total quantities, quantities assigned out, and available quantities remaining). Serialized Gear Inventory Individually tracked items where inventory, historical status, and assignments are maintained by individual unit (serial number), distinctly from general gear. The Vendor is expected to design and implement the most efficient, scalable SPO data schema necessary to deliver a fully functional solution handling these relationships, which may include core tables, lookup lists, workflow state management, and archives. The architecture must support full data lifecycle management, ensuring that inactive core records (e.g., separated personnel, retired inventory) can be archived and removed from active views, but securely maintained for a specified timeframe to meet audit requirements prior to permanent deletion. Once the design is approved, the vendor shall construct the architecture and populate it with synthetic test data to enable rigorous User Acceptance Testing (UAT). The vendor must facilitate testing cycles, incorporate feedback, and perform any necessary reworks identified by the internal team to guarantee the solution's full operability and alignment with mission requirements. The Vendor will provide structural templates and technical guidance to the internal team. The internal team will be solely responsible for the extraction, transformation, and loading of the live Access 2003 data into the new platform. 2.3 Application, Workflow, & Security Scope Using the synthetic test data, the vendor shall develop and refine through repeat testing a unified Power Apps interface and Power A…