Store all data in your format with low effort
All your data can be stored centrally in Sandbank.
Available transfer paths:
- OAuth direct integrations
- Custom API interfaces
- Guided CSV/XLSX upload
Sandbank uses a layered storage model so raw-data information remains preserved.
During transfer, you can choose among three storage modes:
- Store complete dataset
- Store selected subset only
- Store only data bound to Sandbank dashboards (automated transfer paths)
Make imported data visualization-ready through guided mapping
For dashboard visualization, metrics must be mapped to corresponding dimensions. For OAuth direct integrations, this is handled automatically.
Data uploaded via CSV/XLSX or custom API must be mapped once through a visual schema editor, then it becomes available in dashboards.
This means custom source schemas do not need manual restructuring before import.
Which import path to use
Each import path has advantages and constraints.
Choose based on refresh requirements and source availability.
| Import path | Typical source | Advantages | Constraints |
|---|---|---|---|
| OAuth direct connection | Ads, CRM, marketing tools | Fast setup, automated transfer and mapping, near real-time updates | Connector must be available in Sandbank |
| Custom API | Internal CRM, ERP, internal systems | One-time technical setup, automated transfer, near real-time updates | Technical setup and one-time schema mapping required |
| CSV/XLSX | Accounting exports, point-in-time exports | Fast manual entry path | No automated transfer, manual refresh required |
Benefits of a central data infrastructure
- Central access to all relevant data
- Dashboards can be created quickly via templates
- Fact-based decision foundation
- Access control across roles
- Lower overhead for specialized IT and BI staffing
Recommendations
- Define import slots and owners for trigger, validation, and release.
- Set one fixed control checkpoint per source.
- Keep a simple 3-step incident flow for import failures.
Clear responsibilities create structured operations. For example: one data owner connects, maintains, and validates sources; one product owner handles internal product questions; one team admin manages invitations, roles, and access rights.
Related topics
Once storage workflow is stable, continue with Visualizing Data.
For data logic background, Data Structure is the next step.
SANDBANK
Contact
We are happy to help and advise you, send an email to hi@sandbank.cloud.
Information about roadmap updates and submitting or voting on suggestions is available at /development.