Which SAP ECC objects don't map cleanly into SYSPRO and what should we do about them?
Five entity types require workarounds rather than direct field mapping: AR and AP line items (mapped to AR/AP Invoices, but only open items are recommended for migration), Production Orders (AUFK maps to Work Orders with potential loss of routing details), Stock balances (MARD/MCHB mapped per warehouse, but batch splits need lot tracking configured in SYSPRO first), and Condition Records/Pricing (complex SAP pricing conditions are flattened into SYSPRO Price Lists, losing condition hierarchies). For each of these, your team should agree before migration begins on which data to carry across, what to reconstruct manually in SYSPRO, and whether historical closed items are needed at all.
SAP ECC doesn't have a REST API — how do you actually extract the data?
Standard SAP ECC has no native REST API; extraction relies on RFC/BAPI calls, and where standard BAPIs don't cover all required fields (which is common), we use RFC_READ_TABLE for direct table reads or custom Z-BAPIs. Large extractions are broken into batches to avoid SAP memory and timeout limits, and the RFC user account must be provisioned with precise authorization objects (S_RFC, S_TABU_DIS, and object-specific authorizations) before extraction can start. If your landscape uses SAP Gateway OData services as an add-on, we can work with those too, but they typically require custom service generation per object and are not available by default.
Does historical or archived SAP data — like closed invoices or archived documents — come across to SYSPRO?
Documents archived via SAP ArchiveLink are not accessible through standard BAPIs or RFC_READ_TABLE and require a separate extraction step; you should confirm with your SAP basis team which document types have been archived and whether retrieval is feasible before scoping the migration. Posted history is usually loaded into SYSPRO as opening balances or reference data, rather than re-posted as live transactions. Agree on a clear cutover date so that anything posted in SAP after that point is handled by your go-live process rather than the migration.
What has to exist in SYSPRO before the migrated data can actually load?
SYSPRO's e.net business objects enforce referential integrity at import time, so GL accounts, warehouse records, tax codes, and supplier/customer records must exist before dependent transactions (Purchase Orders, Sales Orders, AP/AR Invoices, Stock balances) can be imported without errors. This means the migration runs in a specific sequence: master data first, then transactional data. If your SYSPRO company is newly configured, your implementation team — not ClonePartner — is responsible for setting up the base configuration such as company structure, tax tables, and warehouse codes; we migrate the content once the target is ready to receive it.
What happens to SAP custom fields (Z-fields, append structures, CI includes) during the migration?
Standard SAP BAPIs and RFC calls do not expose custom Z-fields or fields added via append structures and CI includes, so these require custom extraction logic on the SAP side. On the SYSPRO side, custom form fields are stored in separate plus tables (for example, ArCustomer+ for customer extensions) and must be mapped and loaded independently from the main business object payload. Both sides of this need to be identified and scoped before migration starts; any custom fields not surfaced during scoping will not be migrated.
How does SAP's complex pricing model translate into SYSPRO Price Lists?
SAP ECC pricing conditions stored in KONV and the A-tables support multi-level condition hierarchies — customer-specific, material-specific, scale pricing, and surcharges — that have no direct equivalent in SYSPRO's Price List structure. The migration flattens these into SYSPRO Price Lists on a best-effort basis, which means composite or formula-based conditions need to be reviewed and recreated manually in SYSPRO after the data lands. Before migration, your pricing team should export and document the active condition records from SAP so nothing is lost in translation, particularly for customer-specific or contract pricing that isn't visible in standard price list outputs.
Superhuman Docs (Coda)
Claude, 
ChatGPT or 
Cursor. Describe the move in plain English; the agent runs it.
Notion
Slab
ConfluenceSoon
Google DocsSoon
