Migration
From a legacy POS
- Export the catalog (products, customers) and load it into LX CloudPos.
- Configure the P12 certificate and the Hacienda credentials on the tenant.
- Create the API keys for the integrating systems.
- Test in parallel for 1–2 weeks (issuance continues in both the legacy system and LX).
- Migrate the webhooks in reverse order.
- Shut down the legacy system once the migration is verified.
From other APIs (Codisa, ATV, etc.)
These APIs are conceptually similar, but the schemas differ. Notes:
- LX uses a numeric
idProducto; others may use a SKU as a string. - LX calculates totals internally; others may require the total to already be calculated.
- LX signs with the registered P12; others may request the P12 on every call.
For complex migrations, contact support to define a custom plan.