Pre-migration data extraction checklist
Before cutover, operators need a repeatable list of what to pull, what to verify, and what should be preserved for rollback or post-migration reconciliation.
What this article covers
The datasets that matter most before a gate cutover
Where browser-driven extraction can help when API coverage is limited
How to frame extraction as an operational checkpoint instead of a one-off export
Data extraction and validation
Data Extraction: Data Priority Source Method ------ ---------- -------- -------- Tenant-to-code mappings Critical SiteLink/StorEdge Browser agent or SiteLink API (NDA) Gate group definitions (names, hours, days) High SiteLink Setup > Gate Browser agent Gate group keypad assignments High SiteLink Setup > Gate > Gate Groups Browser agent Gate group unit/customer mappings High SiteLink Gate Groups detail pages Browser agent Non-tenant codes (managers, fire dept) High SiteLink tenant records (accounts without rentals) Browser agent Activity/event history Low PDK Cloud Node / Storable backend Not extractable -- accept the loss The SiteLink API (DEI -- Data Exchange Interface) is NOT publicly documented. Access process: Email apisupport@sitelink.com Sign NDA Receive password-protected PDF documentation Set up Corp User account with API rights Pay monthly API fee Obtain API key Architecture: SOAP protocol.
Data extraction and validation (2)
Pre-Migration Data Extraction: This is where Storify's existing browser automation architecture (Browser Use) becomes a competitive weapon:
Browser Agent Path (Recommended): Since the facility already has SiteLink/StorEdge credentials, a browser agent can: Log into the facility's management portal (facility provides credentials) Navigate to tenant list -- extract all tenant-to-code mappings Navigate to Setup > Gate > Gate Groups -- extract group definitions, hours, keypad assignments Navigate to each Gate Group's detail page -- extract unit and customer mappings Navigate to Reports > Gate Activity Log -- extract recent activity (if accessible) Export everything as structured JSON Interface locations: SiteLink Web: Operations > Access (tenant screen Gate Access tab) SiteLink myHub: https://myhub.smdservers.net/ StorEdge: Cloud dashboard under tenant management Storable Easy: Setup > Gate, Reports > Facility > Gate Activity Log ---
Pre-Migration Data Extraction: This is where Storify's existing browser automation architecture (Browser Use) becomes a competitive weapon:
Migration implications
Data Migration Implications for Storify: Data Category Source System Extraction Difficulty Method -------------- -------------- ---------------------- -------- Tenant-to-code mappings SiteLink/StorEdge database Medium SiteLink API (requires NDA + contract) or CSV export from tenant reports Gate group definitions (names, hours, days, keypad assignments) SiteLink/StorEdge database Hard No confirmed API endpoint. Manual recreation likely needed.
Migration implications (2)
Data That Needs Migration: Data Category Source System Extraction Difficulty Method -------------- -------------- ---------------------- -------- Tenant-to-code mappings SiteLink/StorEdge database Medium SiteLink API (requires NDA + contract) or CSV export from tenant reports Gate group definitions (names, hours, days, keypad assignments) SiteLink/StorEdge database Hard No confirmed API endpoint. Manual recreation likely needed.
Next steps
Treat this as a reusable checklist before any facility-specific cutover window is locked.
References