Map before load
Align loan, borrower, investor, and capital fields to CapGrowth OS structures before importing production balances.
Implementation
From Discovery to Post-Launch
A structured onboarding path — not a DIY dump. Many deployments target a few weeks depending on data quality and scope.
Timeline
Ten Steps to Operating on CapGrowth OS
Each step is scoped to your loan book, capital structure, users, and reporting needs.
1
Discovery
Clarify loan products, investor model, company structure, current tools, and must-have workflows.
2
Scope & Plan
Agree on modules in scope, migration depth, portal needs, roles, and a realistic go-live window.
3
Environment Setup
Provision company context, branding, settings, and initial administrative access.
4
Configuration
Configure loan products, users and RBAC roles, operational defaults, and portal-facing settings.
5
Data Mapping
Map spreadsheet or legacy fields for loans, borrowers, investors, and capital balances.
6
Migration & Reconciliation
Load core records and validate balances, participation, and loan status before cutover.
7
Role Training
Train owners, officers, collections, accountants, and viewers on daily workflows and portals.
8
UAT
Run acceptance scenarios: origination/servicing, payments, collections, investor views, and exports.
9
Go-Live
Cut over with a clear support window so the first operating days stay controlled.
10
Post-Launch
Stabilize reporting habits, refine permissions, and address follow-up configuration items.
Requirements
What Clients Typically Provide
Cleaner source data shortens migration and reconciliation.
- ✓Company information and branding assets
- ✓Loan book with current balances and status
- ✓Borrower and investor records
- ✓Business and investor capital balances
- ✓Loan product definitions
- ✓User list with intended roles
- ✓Operating policies for payments, collections, and approvals
Expectations
What Implementation Is Not
Honesty helps go-live succeed.
- —Not a same-day dump of messy files into production
- —Not an automatic replacement of every external accounting system
- —Not MFA/SSO onboarding (those are not advertised as available today)
- —Not unlimited custom development during standard onboarding
Migration
From Spreadsheets and Fragmented Files
Most clients start from workbook exports. Mapping and reconciliation matter more than speed.
Reconcile balances
Validate loan status, participation, and capital totals against source books before cutover — not after the first investor question.
Scope history depth
Core operational records can migrate when source data is complete enough. Exact history depth is agreed in discovery.
Training
Role Sessions Before Go-Live
Training is built into implementation — owners, loan officers, collections, accountants, and viewers.
Go-Live
Controlled Cutover
Go-live is a planned window with acceptance criteria — not a silent flip.
- ✓UAT scenarios signed off for core workflows
- ✓Users provisioned with correct RBAC roles
- ✓Reconciled opening balances for loans and capital
- ✓Support window defined for the first operating days
Support
After Launch
Post-launch stabilizes reporting habits and follow-up configuration.
- ✓Support Center for FAQ and contact paths
- ✓Docs and Knowledge for operator reading
- ✓Permission and reporting refinements as habits form
FAQ
Implementation Questions
How long does implementation take?
Many deployments target a few weeks with structured onboarding — discovery, configuration, data migration, training, and go-live — depending on data quality and scope.
What do we need to provide?
Company information, loan book, borrower and investor data, capital balances, loan products, branding assets, user list, and your operating policies/workflows.
Do you train our team?
Yes. Implementation includes role-focused training for daily operations, payments, reporting, and portals. See Training for role paths.
Can we migrate from spreadsheets?
Yes. Most clients start from spreadsheet or fragmented file exports. We map and migrate loan, investor, and capital records with reconciliation checks.
Will historical data come across?
Core operational records can be migrated when source data is complete enough. Exact history depth is scoped during discovery.
Can we run multiple companies?
Yes. CapGrowth OS supports multi-company operations with company switching and tenant isolation. Multi-entity scope is confirmed during planning.
What support exists after go-live?
Post-launch support covers stabilization, permission refinements, and operational questions. Use the Support Center, FAQ, and contact form.