Choose where your data lives
Keep the destination database and its operational ownership in your environment. Plan the network, credentials, capacity and database recovery together.
Salesforce / Data Migration
Your Salesforce data. In your own database.
Bring selected Salesforce records, relationships and files into infrastructure you control. Define the scope, capture the data and validate independent retrieval before making source-retirement decisions.
A scoped migration engagement using Vivly's archive capture workflow. Destination and deployment compatibility are confirmed during assessment.
- 01Your Salesforce org
Selected objects, fields, relationships and files
- 02Scoped capture
Preview, copy, track progress and reconcile
- 03Your database
On-premises or cloud-hosted, with verified retrieval
The copy preserves selected data. Source access remains in place until your team has validated the result and approved the next step.
Keep the context with the records
Include the parent and child relationships, activities and accessible files that make the selected history useful beyond Salesforce.
Make acceptance measurable
Agree the object scope, record checks, relationship checks and file verification before capture. Test the destination reads your teams actually need.
The workflow
A migration starts with a verifiable copy.
Use the archive capture foundation for a defined data extraction engagement. Set the destination and acceptance criteria before moving the first record.
- 01
Scope the Salesforce data
Select standard and custom objects with filters or SOQL. Identify dependencies, accessible files, source permissions and the history required by downstream users.
- 02
Prepare your database
Confirm the engine and host, provision credentials and storage, and agree the destination structure. The SQL Server capture path uses typed object tables and overflow fields for unmapped or compound values.
- 03
Capture and reconcile
Run the scoped copy with job progress and checkpoints. Review failures and reconcile records, relationships and files against the agreed source scope.
- 04
Validate independent use
Test retrieval and downstream queries from the destination. Any final refresh, change freeze, cutover or Salesforce retirement is a separately planned and approved activity.
On premises or in your cloud
Your database.
A defined deployment.
Choose where the data lives. Agree the engine, network access, permissions, storage capacity and recovery responsibilities before rollout.
Read the deployment guides| Database | What to plan for |
|---|---|
| SQL Server | The reference capture implementation writes typed object tables to a customer-controlled SQL Server database. Validate your on-premises or cloud-hosted installation. |
| Other database engines | Discuss PostgreSQL or MySQL deployment variants during assessment. Confirm feature scope and acceptance before committing to a destination; arbitrary database targets are not assumed. |
- On premises
- Plan service placement, firewall rules, database connectivity, storage and operational ownership inside your infrastructure.
- In your cloud
- Use your cloud environment with an agreed database engine and network path. Managed database compatibility requires a deployment review.
- Data shape
- Preserve the captured Salesforce record model and provenance. Transformations into an existing application schema require separate mapping and validation.
- Source continuity
- Capture spans a time window. Continuous change-data capture, automatic cutover and zero-downtime migration are outside this workflow.
Before you begin
Know the scope.
Can Salesforce data move to an on-premises or cloud database?
Yes, a scoped copy can place selected records and files in your database. SQL Server is the reference capture path. Confirm the database engine, host, permissions and acceptance criteria for your intended environment.
Does this migrate the entire Salesforce application?
The engagement covers selected data and its captured relationships and files. It does not recreate Salesforce metadata, Apex, flows, page layouts, sharing rules or a replacement CRM application.
Will copying delete records or switch off Salesforce?
No. Copying leaves the source in place. Source cleanup is disabled by default, and retirement requires a separate plan covering completeness, final changes, retrieval, retention and approvals.
How is migration different from archive or backup?
Migration establishes an agreed data copy in a destination for independent use. Archive keeps inactive history accessible. Backup creates recovery snapshots with controlled restore to the original Salesforce org. Choose the workflow based on the outcome you need.
Can we use an existing database schema?
The capture path has its own destination structure. Mapping into an existing schema, changing identifiers or integrating downstream applications needs a separately agreed transformation and validation scope.
Start with your Salesforce data.
Bring the objects, files, destination and outcome you have in mind. We will define the scope and acceptance checks together.