Legacy system cleanup

    Clean up legacy systems without breaking what depends on them

    Rig maps every field, rule, report and integration your old CRM and ERP still run on, so each change ships in a safe order and reporting stays steady throughout.

    Discuss your legacy systems

    Old systems still run the business, and nobody knows what they touch

    Years of acquisitions and admins leave a CRM full of fields, rules and code nobody documented, an ERP on a version the vendor is retiring, and integrations only one person understands. Every change risks breaking commissions, finance or a report the board reads, so cleanups stall and the old systems keep running.

    1. 31 Dec 2025

      Salesforce ended support for

      Workflow Rules and Process Builder

      With Rig

      They still run, but Salesforce no longer fixes bugs in them. Rig shows which rules still fire and what each one touches, so your admins rebuild those and retire the rest.

    2. 11 Jan 2027

      Microsoft ends extended support for

      Dynamics NAV 2017 and BizTalk Server 2016

      With Rig

      The NAV history syncs into a warehouse you own before the server goes, and the map shows every BizTalk flow the replacement has to cover.

    3. 11 Jan 2028

      Microsoft ends extended support for

      Dynamics NAV 2018

      With Rig

      Your reports keep the same numbers before and after the move to Business Central, because they read the warehouse.

    4. 31 Dec 2029

      Microsoft ends support for

      Dynamics GP

      With Rig

      A partner moves the transactions, and Rig keeps the years of history the standard migration leaves behind, plus the reports that read it.

    What happens to each legacy layer

    Nothing is switched off until the map shows nothing depends on it.

    • Undocumented fields

      A field catalogue

      Each custom field is listed with the rules, flows, code and reports that read it, and whether anyone still writes to it.

    • Rules nobody owns

      A change map

      The map shows which automations still fire, which fields they touch, and which reports and systems they feed.

    • Reports that shift

      Warehouse reporting

      Reports read synced data in the warehouse, so pipeline and revenue keep their numbers while fields and rules change.

    • History the new ERP drops

      Warehouse tables

      Years of transactions sync into a warehouse you own before the old server is retired, and stay queryable for audits and trends.

    • Integrations one person understands

      Flows on the map

      Every flow between systems is drawn with what it moves and what depends on it, so whoever builds the replacement starts from a full list of what each flow moves.

    • Definitions that drifted

      Certified metrics

      Pipeline, ARR and churn are defined once, so a rebuilt rule cannot quietly change what a stage or an amount means.

    How the work runs

    1. Audit what runs

      We map fields, rules, flows and code on read-only access, plus every report and system that reads them. The price is fixed before we start, and the map arrives in weeks.

    2. Rank every change

      Each field, rule or system gets a red, amber or green verdict and a safe order for removal, which is what your admins take to approval.

    3. Keep reporting steady

      Objects and history sync into a warehouse you own, and reports are rebuilt there and checked against the originals.

    4. Retire with the map open

      Your admins or partner retire, rebuild or migrate each piece with the map in front of them, and our engineers can do the work alongside them.

    Which system are you cleaning up?

    SalesforceDynamics and Business CentralSQL Server reporting

    Where to start

    Common questions

    Do Workflow Rules and Process Builder still run?

    Yes. Salesforce ended support on 31 December 2025, so existing rules keep firing but bugs are no longer fixed. Salesforce points customers to Flow, and the audit lists which rules still need rebuilding there.

    How does the audit work?

    We map which rules, flows and code run, which fields they touch, and which reports and integrations read those fields. Your admins can use the map whether or not anything else happens with us.

    Does Rig replace Salesforce or our ERP?

    No. Your team keeps working in them. Rig maps them, keeps their history and runs the reporting around them. If you decide to move a system, Migrate scopes that move from the same map.

    What happens to history the new ERP will not import?

    A standard migration usually brings opening balances and master data, and years of transactions stay in the old database. We sync that history into your warehouse before the old system goes, so old invoices and ledger entries stay queryable.

    Can reporting stay steady during the cleanup?

    Yes. Reporting moves onto the warehouse first, before any field or rule changes.

    Do you need access to production data?

    Not at first. The map of fields and rules comes from metadata, and access starts read-only and least-privilege. Wider permissions follow only for the phase you approve.

    SOC 2 Type 2EU and US hostingRole-based accessYour warehouse or ours

    Talk to Rig

    What work do you want to improve?

    Tell us where your team spends time, loses money or needs better information.
    In a 30-minute call, we’ll discuss the data and systems work that could help.

    Discuss your legacy systemsUse the platform with your team, or add our engineers.