Implementation and migration

Legacy history connected to Salesforce

Historical records belong in dedicated archive objects, linked to current records without triggering operational automation.

Built for: SMT Research, Vancouver
Service line: Implementation and migration
Window: Jun to Sep 2026

The headline number16Archive objectsTechnical schema count. Transaction values and financial findings are confidential.

01Key numbers

What we measured

16Archive objectsTechnical schema count. Transaction values and financial findings are confidential.

02The situation

What was true before

Historical records belong in dedicated archive objects, linked to current records without triggering operational automation.

Recognise this in your own org?

Start a diagnostic See the service lines

03What we built

The mechanism

The public case describes the implementation. Client financial data and findings are withheld under NDA.

Separate archive objects

Load historical data into dedicated objects and preserve source-system keys.

Reconciliation before cutover

Compare migrated records with their sources and route exceptions to authorised reviewers.

Sales and Forecasting

CountProductsBulk editSpot checkHistoryAudit log

Start a physical inventory count

412 products selected. Only ticked items on the Products tab are pulled in.

Count nameQ3 2026 warehouse countReason for this countQuarterly cycle, plus a variance found on cable reelsStart count

Depiction · A physical stock count hub: count, bulk edit, spot check, history and a full audit log, built as one component instead of five reports.Every adjustment requires a reason before it will save. An unexplained stock correction is how a discrepancy becomes permanent, so the field is mandatory rather than encouraged.

Surfaces built

Walkthroughs use demonstration data. Client records remain confidential.

Archive records with source keysImage withheld
Migration validation reportsImage withheld
Exception review filesImage withheld

The finding

Client financial information is confidential.

Amounts, ratios, financial findings and underlying client records are not published.

04Outcome

What changed, verified

The implementation is described through its workflows and controls.

Archive records with source keys
Migration validation reports
Exception review files

How it was verified

Validation compares source records with system outputs. Client records and financial results remain private.

Sources

docs/research/01-salesforce-platform.md §2.4 · ERP migration
docs/research/01-salesforce-platform.md §2.3 · Rollup and data-integrity repair

Keep reading

Two more

All case studies

Implementation and migration
ValidationAt the integration boundaryTechnical capability. Client accounting data is confidential.
An accounting integration with explicit validation
A two-way accounting integration validates record mappings and data precision at the boundary between systems.
Implementation and migration
Audit trailOn stock changesTechnical capability. Stock quantities, valuations and production volumes are confidential.
Inventory movement with an audit trail
Inventory workflows connect receiving, transfers, field use and replenishment with a traceable record of each change.

Next step

Bring us your hardest Salesforce problem

Tell us which Salesforce workflow needs attention. Start with a free fit conversation; we agree scope and fees before paid work begins.