Migrate from RAMM to Microsoft Dynamics 365 Sales

Ramp vendors map directly to Dynamics 365 Accounts. Vendor name becomes Account Name; vendor category becomes Industry or a custom Vendor_Category__c pick-list. Ramp's vendor ID is preserved as an external key on the Account for traceability and delta-run matching during migration.

Ramp employees who hold corporate cards become Dynamics 365 Contacts. Email, name, and department map directly. The contact is linked to the primary Account (employer vendor) via the AccountId lookup. Active card status and employee spend limit are stored as custom fields on the Contact.

Ramp's Card object has no direct Dynamics 365 equivalent — there is no native card management in Sales. FlitStack creates a Corporate_Card__c custom table in Dataverse linked to the Contact cardholder. Fields include card last-four digits, spend limit, merchant lock settings, and issuance date.

Ramp transactions (card charges, bill payments, reimbursements) become records in a custom Spend_Transaction__c Dataverse table. Each transaction links to the Account vendor, the Contact cardholder, and the Card used. Original Ramp transaction ID stored for duplicate detection on re-runs after migration.

Ramp expense reports map to a custom Expense_Report__c entity linked to the employee Contact. Report status (submitted, approved, reimbursed) becomes a status pick-list field. Line items reference Spend_Transaction__c records included in the report. Each report can be linked to multiple transactions, and any supporting documentation is attached to the record for audit trails.

Ramp spend policies (per-card limits, merchant restrictions, receipt thresholds) are not native Dynamics objects. FlitStack stores policy rules as JSON in a custom text field on the Card record and exports a policy inventory to a SharePoint list your admin can use to build Power Automate approval flows.

Ramp merchant category codes (MCC codes) map to Dynamics 365's Industry pick-list where possible. For Ramp-specific categories not in the standard list, a custom Vendor_MCC__c field is added to the Account. Merchant tax ID maps to Dynamics Account's TradingPartnerAccountNumber field if present.

Ramp receipts are image or PDF files attached to transactions. FlitStack downloads each receipt, then re-uploads to the associated Spend_Transaction__c record's document location in Dynamics SharePoint integration. Original receipt URLs preserved as a reference field if Ramp API access remains open.

Ramp's sync status with connected accounting platforms (QuickBooks, Xero, NetSuite) has no Dynamics 365 equivalent. Sync state and last-synced timestamp are stored as custom fields on the Account for finance team reference during cutover and reconciliation for accurate reporting and audit compliance.

Ramp department and team spend budgets map to a custom Department_Budget__c Dataverse entity linked to the Account. Budget amount, period (monthly/quarterly/annual), and current spend are custom fields. Overspend alerts require Power Automate to recreate Ramp's native notifications for your organization.