#mtanzi - subscription migration

1 messages ยท Page 1 of 1 (latest)

delicate pumice
dapper plinth
#

I think I missed the last part of the sentence ๐Ÿ™‚
... so that the migrated subscription would look like started in the past

delicate pumice
#

You cannot modify the created_at but we do have a guide for backdating subscriptions to better capture history outside of stripe.

#

Sorry, I meant preserving settings/cycles

#

Not actual payment histories.

dapper plinth
#

thanks @delicate pumice ! that looks what I am looking at, let me take a look at the doc and see if that fits my purpose!

delicate pumice
#

Happy to help ๐Ÿ˜ Let me know if you still have any questions.

dapper plinth
#

another quick thing.. the subscription might have attached also other addon prices.. that should not change for the backdating?

#

the price have the same cycle of the main subscriptino

#

so the starting date is the same (more or less)

delicate pumice
#

What are you defining as the "main" subscription?

dapper plinth
#

let say...

#

I have a subscription with price1 on the monthly cadence

#

then I have price2 that is an add on that can be added anytyle during the billing cycle

#

it gets prorated and billed from the day we added untill the end of the cycle... then from the next cycle on it follow the price1 cycle

#

hope I manage to explain correctly... it sounds a bit confusing ๐Ÿ™‚

delicate pumice
#

What exactly is the concern? You can add additional prices at any time.

dapper plinth
#

not really a concern just wanted to ask whether there might be some caveat with this configuration when I'll create a backdated subscription

delicate pumice
#

No you can still add one-time prices or prices with the same monthly cadence.

#

If it is in the middle of the billing cycle you will the a prorated amount applied to the next invoice.

dapper plinth
#

ok, that's sounds reasonable ๐Ÿ‘
Thanks again for the support!