MapleJockey expansion: independent content and evidence review
17 November 2026 | Local catalogue and migration-guide increment
Conclusion
No unresolved material content blocker was found in the reviewed release. The catalogue is suitable for a private founder demonstration as an initial source-linked collection of candidates. The guides are suitable as scoped rehearsal designs, not as evidence of completed migrations or approved production changes.
Reviewed: PRODUCT_DIRECTION.md; the existing assessment README; all 45 catalogue entries and 270 claims; the five migration guides; source-reference structure; Canadian-language conventions; and selected consequential claims against primary sources. Browser interaction, visual layout and vendor-account behaviour are not verified by this review.
Verification performed
- All 45 entries retain six distinct dimensions: Canadian connection; ownership and jurisdiction; data residency; support and administrator access; key control; and portability.
- All 270 claims have an ID, date, scope and reason. Their referenced source IDs resolve within the relevant entry. Unknowns remain explicit.
- Re-ran checks/validate_data.py against the combined catalogue and guides: passed.
- The five guides contain scope, prerequisites, sequence, validation, expected losses, rollback, stop conditions and dated source links.
- No em dashes appeared in the reviewed authored product direction, catalogue JSON or guide JSON. Canadian spelling is used in authored copy; official names, source titles and technical identifiers retain their source forms.
- The product direction explicitly says the catalogue is not exhaustive and the incumbent examples are not a measured market-share ranking.
- Canadian founding, headquarters, incorporation, ownership and hosting are not treated as interchangeable.
- Public supplier documentation is not presented as a tenant observation. No blanket sovereignty certification, legal immunity or government endorsement is claimed.
- Contracting/IP and commercial assumptions do not block reversible local work; no approved spending or outreach is implied.
Primary-source spot checks
The following checks substantiate selected claims only. They do not constitute a complete supplier due-diligence exercise.
| Entry or route | Claim checked | Result and primary source |
|---|---|---|
| Magnet Forensics | Canadian headquarters and Thoma Bravo relationship | The current owner portfolio lists Waterloo, Ontario and links the acquisition announcement. Thoma Bravo portfolio |
| D3 Security | Employee ownership | The supplier currently describes employee ownership and customer-funded development. The catalogue correctly treats this as a supplier declaration, not proof of Canadian beneficial ownership. D3 company page |
| Devolutions | Canadian hosting option and international support delivery | Schedule A, version 2026.1, lists Canada among cloud locations and support delivery from Canada, Austria, Germany and Spain. Customer agreements |
| 1Password | Regional storage and service-data exceptions | The privacy notice distinguishes selected secure-data regions, EU item sharing and international service/support processing. Privacy notice |
| Sync.com | Canada or US region; optional encryption exceptions | Current policy describes region-dependent file storage and feature-specific content processing. The guide requires actual tenant confirmation. Privacy policy |
| Hootsuite | Canadian headquarters with US hosting | The trust-centre page expressly describes Canadian headquarters, US AWS content hosting and global auxiliary providers. Trust-centre privacy |
| Borealis | Ontario infrastructure and portable metadata | The technical page supports the scoped infrastructure and API/export claims, but is published 23 June 2022. Its age is now visible. Borealis technical information |
| HubSpot to Maximizer | Company/contact import mapping | Maximizer's current CSV guide describes company-and-contact records and match fields. The MapleJockey guide improves safety by using a bounded test area rather than applying live updates. Maximizer import guide |
| LastPass to 1Password | Supported importer and lost object types | The current importer guide supports folder conversion, shared-folder permission handling and explicit passkey/authenticator/private-history limitations. 1Password importer |
| Mailchimp to Cyberimpact | Consent defaults, exclusion protection and date handling | Current import documentation describes implied-consent treatment for mixed/unspecified sources and protection for existing destination unsubscribes. Preparation guidance says time components are ignored. The runbook preserves original proof and blocks unresolved live sending. Import, format preparation |
Corrections made during review
- Borealis technical material was reviewed now but published in 2022. The author added the publication date to relevant scopes and a limitation requiring current confirmation before migration. A retrieval date no longer resembles a fresh infrastructure attestation.
- Cyberimpact's terms constrain intermediary sending and account use. The migration author clarified that the exercise uses the customer's authorised registered users/account with sending disabled. Terms
Migration safeguards checked
The CRM guide distinguishes records from workflows, integrations, attachments and history. Stable IDs, relationship checks and readback are required.
The marketing guide preserves suppression and evidence separately from contact data. Unknown consent stays excluded; a native suppression test is required before a live send. No messages are sent in the proposed rehearsal.
The password guide uses synthetic secrets, handles plaintext-export risk, checks allowed and denied access and preserves recovery. Unsupported credentials require their own replacement path.
The research file guide includes independent restoration, checksums, usable file formats and permission tests. File copying does not preserve collaborative history or research approvals.
The defence guide selects no destination and copies no sensitive material. Real-data movement remains gated on contract-specific requirements, deployment evidence and the applicable approvals.
Boundaries and follow-up
This review did not exhaustively open all source URLs, validate every ownership chain, authenticate supplier assertions, inspect live tenants or perform a provider migration. Source structure validation cannot establish truth. The source record count is not a count of independent corroborations.
Future catalogue maintenance should store original publication dates where available and distinguish retrieval, validity and review-due dates. Several public-resource entries use Unknown for operational dimensions that may not be relevant to ordinary public-data downloads; a future applicability field could make those entries clearer without converting uncertainty into assurance.
The first vendor rehearsal should use a named workload owner, approved synthetic scope, exact source/target plans, a recorded baseline, measurable functional checks and rollback. Retain the desk-reviewed status until that exercise produces observed evidence.
Browser/UI behaviour is outside this review's verified coverage. The existing local assessment's historical recovery result also remains separate from these unexecuted vendor migration routes.