Migrate an existing line of credit (LOC) portfolio from your legacy system to Peach: prepare your data, create borrowers and loans, populate historical records, execute the migration, and validate the results. This section is for integration engineers running a migration, with concept and reference pages for analysts and operations.
LOC migration uses a statement-based approach. Historical data before the most recent statement date is stored as read-only snapshots; data after that date is replayed by Peach's Loan Replay™ engine.
- LOC migration key concepts — The cutoff date, migration draw, past periods, and historical vs. live activity.
- Before you migrate a LOC portfolio — Prerequisites and timing for the migration window.
- LOC migration procedure — Create the borrower and loan, populate history, create activities, and execute.
- After LOC migration — Validate balances, configure autopay and credit reporting, and post-migration behavior.
- Modify data after LOC migration — Dispute purchases, cancel fees, and change or reverse past transactions.
- LOC migration special cases and configuration — Origination and draw fees, statement scheduling, and special loan states.
- LOC migration strategy and operations — Batching, borrower communications, concurrent operation, and re-migration.
- LOC migration validation and troubleshooting — Validation rules and a troubleshooting FAQ.
- LOC migration API and webhooks reference — Endpoints used across the workflow and webhook events.
- How LOC billing cycles work — Period dates and non-due to due to overdue balance movement.
- How grace periods work for lines of credit — The pay-in-full rule, daily grace tracking, and the due-date-plus-one check.
- How LOC draws work — Draw types, the shared credit limit, and the static migration draw.