People
Available now · Template-based
Admin users can import CSV or Excel files using the provided people template. Required identity fields, optional profile fields and guest/member classification paths are defined.
Onboarding and data preparation
Review how a ministry can prepare the workspace, team, data and first connected workflow. This page is informational. It does not start onboarding or collect organisation details.
The preparation principle
Suggested rollout
The sequence is guidance rather than a managed onboarding commitment. Each ministry remains responsible for validating its records, permissions and rollout decisions.
Confirm organisation, region, currency, timezone and the core operational owner.
Invite only the core team, review roles and give each user the permissions required for their work.
Clean identity fields, decide member/visitor classification and avoid importing unnecessary sensitive data.
Create a programme, prepare attendance and follow one responsibility path from record to review.
Open only the member journeys the church is ready to operate, review and support.
Reconcile the sample, resolve errors and confirm ownership before bringing in more records.
Verified import boundaries
The marketing website does not accept uploads. Import tools are available only inside an authorised workspace and apply file, row, validation and permission controls.
Available now · Template-based
Admin users can import CSV or Excel files using the provided people template. Required identity fields, optional profile fields and guest/member classification paths are defined.
Available now · Review before commit
A template-based assistant validates transaction rows, category alignment and journal readiness before an authorised user commits the reviewed batch.
Available now · Aggregate history
CSV or Excel templates can import service-date aggregate counts. This is not a person-by-person attendance-history migration.
Available now · Template-based
An authorised admin can import an equipment or property register with category, purchase, location, condition and optional asset-tag fields.
Unsupported · Manual setup required
People can be imported, but household and programme batch-import lanes are not implemented in the current import workspace. Set up these structures separately.
Separate workflow or unsupported
Opening balances use the finance journal workflow. Suppliers and other unlisted record types are not presented as supported public import capabilities.
Begin with a small validated sample.
Review duplicates, required fields, classification, errors and reconciliation before importing a complete historical dataset. Do not upload confidential files through the marketing website.
Support expectations
StewardOS has API documentation and selected in-product guidance. Complete account documentation, public response times, plan-specific service levels, priority onboarding and migration assistance remain undefined.
Limited · Not established
The public /docs route is API documentation. Selected in-product help exists, but complete account, billing, closure and data-lifecycle documentation is not established.
Available
Setup, launch and module guidance exists inside the application, with scope varying by workflow.
Approved contact channel · Service level undefined
The approved StewardOS email address is available for product enquiries. Coverage, eligibility and response times are not published.
Preview architecture only
The public request route is designed but does not yet accept, store or send requests.
Not a current public commitment
Scope, eligibility, scheduling, response time and plan treatment require an approved operating model.
Not a current public commitment
Template-based product import tools do not create a promise of managed migration, data cleansing or reconciliation services.
See StewardOS in action, then email joshowusu@gmail.com to arrange onboarding during this limited launch.