Can you automate the work before replacing the old ERP?

Yes. A custom platform can coordinate work with an existing ERP while parts of the operation move to a new system. Depending on available access, that connection can use APIs, structured files or RPA that interacts with the existing application's interface.

This approach lets a business improve a defined workflow before completing a larger replacement. It also requires a clear decision about which system owns each record during the transition.

Choose the connection around the application

Start by establishing what the current system supports. A documented interface may provide a reliable route for reading and updating records. A supported import or export can be appropriate for a scheduled exchange.

Where those options do not cover the required work, RPA may operate the application through its screens. Microsoft documents this pattern for applications without suitable APIs in its SAP RPA guidance.

The presence of a robot does not make every integration simple. Permissions, interface changes, available environments and business rules still determine what can be automated reliably.

Give the robot a bounded business task

A useful task has a defined input, a permitted action and a result that can be checked. For example, it might create an approved record in an existing system and return that system's reference.

The workflow should know whether the record already exists. If the application becomes unavailable after a save, the next run must establish what happened before attempting another creation.

That confirmation is especially important when work crosses systems. A successful click is not enough to establish that the business transaction completed correctly.

Separate interpretation from execution

AI can help interpret a document, classify a request or prepare a proposed update. The action that changes an established system should follow defined rules and permissions.

This separation gives the business a place to review uncertain interpretation before it becomes an operational commitment. It also makes it easier to investigate a failure: was the source misunderstood, the action rejected or the result not confirmed?

Keep the transition understandable

As a workflow moves, decide which platform owns the customer record, the operational order, the accounting document and other relevant data. Ownership may differ by record type.

Avoid a situation where both systems can change the same information without a reconciliation rule. Show pending updates and failures to the responsible team. A temporary integration still needs an owner, support and a recovery procedure.

Replace components when there is a reason

Some parts of an established ERP may continue to serve the business well. Others may require an expensive workaround for every operational change. A phased approach lets the company assess these boundaries using real work.

This can apply in an environment containing SAP, Microsoft Dynamics NAV or Oracle, but the exact product, version, interfaces and contractual access must be assessed. It is not a blanket claim that every platform or module is interchangeable.

Discuss a phased modernization with Perspective Unity. We can identify a useful workflow, its current system dependencies and a practical integration path.

Written by the Perspective Unity team. Workflow diagrams are editorial illustrations.