Beem Systems Site Logo

WordPress Migration & Technical Audit SOW

Exhibit A – Statement of Work

WordPress Hosting Migration & Technical Audit

This Statement of Work (“SOW“) is incorporated into and governed by the Beem Systems Tech Services Agreement (“Agreement“). Capitalized terms not defined in this SOW have the meanings assigned to them in the Agreement.

1. Project Objective

Service Provider will migrate Client’s existing WordPress e-commerce website from its current hosting environment to a new Client-owned managed hosting environment, validate material business functionality following migration, establish a staging environment, and conduct a technical audit of the migrated website.

The engagement is intended to accomplish two distinct objectives:

  1. Move the existing production website to a stable destination hosting environment while preserving its material existing business functionality.
  2. Evaluate the website after migration and provide Client with documented findings and recommendations concerning technical condition, reliability, performance, security, maintainability, software configuration, database health, and product configuration.

The migration is not intended to modernize, redesign, optimize, or remediate the website during the move except for adjustments reasonably necessary to complete the migration.

2. Project Fee

The fixed project fee is $1,500, payable in full before work begins.

The project fee covers the Services expressly described in this SOW. The fee is fixed for the defined scope and is not based upon hours worked.

All payments are subject to the payment and no-refund provisions of the Agreement.

Third-party hosting, software licenses, subscriptions, transaction fees, and other third-party expenses are not included unless expressly stated otherwise.

3. Destination Hosting

Client will establish and maintain the destination managed hosting account in Client’s own name and will pay the hosting provider directly.

Client will provide Service Provider with appropriate authorized administrative access necessary to configure the destination environment, perform the migration, and complete the Services.

Service Provider may recommend hosting specifications appropriate to the website based upon available information and observed requirements. Hosting provider pricing, availability, specifications, policies, and future changes remain outside Service Provider’s control.

4. Phase 1 – Production Migration

Service Provider will perform a controlled migration of the existing production WordPress website to the destination hosting environment.

The migration will include the website components reasonably necessary to migrate the existing production system, including, as applicable:

  • WordPress application files and configuration;
  • WordPress database;
  • media library and uploaded content;
  • themes and child themes;
  • active plugins required by the existing website;
  • WooCommerce configuration and data;
  • products and product data;
  • customer records;
  • existing order history;
  • product attributes and variations;
  • existing product options and customization functionality;
  • applicable WordPress configuration;
  • hosting-related configuration reasonably necessary for operation in the destination environment;
  • SSL configuration; and
  • domain and DNS cutover coordination.

The objective of the migration is to preserve the website’s material existing business functionality, not to correct all defects or deficiencies in the source system.

Service Provider may make reasonable environment-specific adjustments necessary to operate the migrated website in the destination hosting environment. Such adjustments are part of the migration and do not constitute separate remediation.

Pre-existing defects, legacy software conditions, configuration problems, data issues, or other deficiencies do not become migration remediation obligations merely because they are discovered or remain present after migration.

5. Production Cutover

Service Provider will coordinate the final production cutover.

To reduce the risk of missing or conflicting e-commerce transactions, Service Provider may establish a brief maintenance period, order freeze, content freeze, or other controlled cutover window while the final production data is transferred and the destination environment becomes authoritative.

Client will reasonably cooperate with the cutover process and avoid changes or transactions during any agreed freeze period.

The source hosting environment will remain available during initial migration validation where reasonably feasible. Client will not cancel or disable the source environment until Service Provider advises that it is no longer reasonably required for migration fallback purposes.

6. Phase 2 – Production Validation

After cutover, Service Provider will perform reasonable validation of material business functionality in the destination production environment.

Depending upon the website’s existing configuration, validation may include:

  • public website availability and primary navigation;
  • representative product pages;
  • material product attributes and variations;
  • material product customization functionality;
  • cart operation;
  • checkout operation;
  • payment integration;
  • material shipping functionality;
  • customer account access;
  • order administration;
  • transactional email;
  • WordPress administrative access;
  • domain and SSL operation; and
  • destination hosting and backup functionality relevant to normal production operation.

Validation will use representative testing appropriate to the website and does not constitute exhaustive quality assurance of every page, product, variation, customization combination, historical transaction, browser, device, shipping scenario, payment scenario, or third-party integration.

Service Provider will address migration-related configuration issues reasonably necessary to make the destination environment operational within the scope of this SOW.

Correction of pre-existing application defects or other conditions unrelated to the migration itself is not included merely because such conditions are observed during validation.

7. Phase 3 – Staging Environment

After the destination production environment has been reasonably validated, Service Provider will establish a staging environment for technical evaluation and testing.

The staging environment may contain a copy of production website and database information for purposes of performing the audit.

Service Provider may disable, redirect, suppress, or otherwise modify functions in staging that could create unintended production effects, including:

  • payment processing;
  • customer-facing email;
  • search engine indexing;
  • webhooks;
  • scheduled processes; and
  • external integrations.

Staging is a testing environment and is not intended to behave identically to production in every respect.

8. Phase 4 – Technical Audit

Service Provider will conduct a technical review of the migrated website using professional judgment to determine which areas warrant investigation.

The audit may include review of:

  • WordPress core and configuration;
  • theme and child-theme configuration;
  • active and inactive plugins;
  • obsolete, abandoned, redundant, or unnecessary software;
  • plugin dependencies and compatibility;
  • software licensing considerations;
  • suitability of existing software for current business requirements;
  • opportunities to consolidate or replace legacy components;
  • WooCommerce configuration and extensions;
  • product catalog architecture;
  • product attributes and variations;
  • product options and customization methods;
  • database size, structure, and accumulated data;
  • scheduled tasks and background processes;
  • performance and caching configuration;
  • security configuration and material security concerns;
  • backup and recovery configuration;
  • transactional email configuration;
  • hosting and server requirements; and
  • other material technical conditions discovered during the audit.

The audit is a professional technical assessment, not an exhaustive certification or guarantee that every defect, vulnerability, incompatibility, data issue, licensing issue, or other technical condition will be discovered.

9. Product Variations and Customization Review

The audit will specifically review how the existing WooCommerce catalog uses product variations, options, and customer customizations.

Product variations generally represent distinct versions of a product that may affect SKU, inventory, pricing, or availability.

Product customizations generally represent customer-selected options such as embroidery, personalized text, or other selections that do not necessarily represent separately inventoried products.

Service Provider will evaluate whether the existing product configuration reasonably distinguishes these requirements and whether the current software architecture remains appropriate.

The review may include the existing use of WooCommerce Product Add-Ons and related product-option functionality.

Recommendations may include retaining, reconfiguring, consolidating, restructuring, or replacing existing product-option functionality.

Implementation of such recommendations is not included in this SOW unless an adjustment is reasonably necessary solely to complete the production migration.

10. Audit Findings and Recommendations

After completing the technical audit, Service Provider will provide Client with documented findings and recommendations concerning material conditions identified during the review.

Recommendations may include:

  • retaining existing components;
  • reconfiguring existing components;
  • removing unnecessary or obsolete software;
  • replacing unsuitable or unsupported software;
  • restructuring portions of the product configuration;
  • database cleanup or maintenance;
  • performance improvements;
  • security improvements;
  • reliability improvements;
  • hosting or infrastructure changes;
  • operational improvements; and
  • simplification of the technology stack.

Recommendations represent Service Provider’s professional assessment based upon information reasonably available during the audit.

Client determines which recommendations, if any, Client wishes to implement.

11. Remediation and Additional Services

The technical audit identifies and recommends; it does not include implementation of the recommendations.

Except for work reasonably necessary to complete the migration and production validation, the $1,500 project fee does not include:

  • implementation of audit recommendations;
  • replacement of plugins, themes, or other software;
  • substantial plugin or application reconfiguration;
  • custom development;
  • website redesign;
  • substantial product catalog restructuring;
  • database cleanup or remediation;
  • security remediation projects;
  • performance optimization projects;
  • new integrations;
  • ongoing website maintenance;
  • ongoing hosting administration;
  • ongoing technical support;
  • third-party software licenses;
  • hosting charges;
  • domain fees;
  • payment processing fees; or
  • third-party subscription services.

If Client wishes to proceed with recommended remediation or other additional Services, Service Provider will separately define the applicable scope and price. No additional billable work will be performed without Client approval.

12. Project Completion

The Services described in this SOW will be considered complete when Service Provider has:

  • migrated the production website to the destination hosting environment;
  • performed reasonable production validation;
  • established the staging environment;
  • performed the technical audit; and
  • delivered the audit findings and recommendations to Client.

Completion is not dependent upon Client accepting or implementing any audit recommendation or purchasing additional Services.